Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2021-47401ipack: ipoctal: fix stack information leak

Description

In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix stack information leak The tty driver name is used also after registering the driver and must specifically not be allocated on the stack to avoid leaking information to user space (or triggering an oops). Drivers should not try to encode topology information in the tty device name but this one snuck in through staging without anyone noticing and another driver has since copied this malpractice. Fixing the ABI is a separate issue, but this at least plugs the security hole.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 2 years later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2021-47401, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.1CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.25% · top 83% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.1.

Affected products

  • Linux · Linux

    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < acb96e782bad427ca4bb1bd94af660acd1462380
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < 741ea2670e021350e54f491106bdaa22dc50e6a0
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < 2725925982dc96a78069cd118ea3d66759bfdad7
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < 829f13d6079cf7a2465522f39acb43033e9b320d
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < 8657158a3b68c85234e6da3d8eae33d6183588b7
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < 5f6a309a699675680df15d9b6d389114515b4426
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < 0a9c36a2e06a249acbed64e8e0b84637c2ad7575
    • affected ba4dc61fe8c545a5d6a68b63616776556b771f51 – < a89936cce87d60766a75732a9e7e25c51164f47c
  • Linux · Linux

    • affected 3.5
    • unaffected < 3.5
    • unaffected 4.4.286 – ≤ 4.4.*
    • unaffected 4.9.285 – ≤ 4.9.*
    • unaffected 4.14.249 – ≤ 4.14.*
    • unaffected 4.19.209 – ≤ 4.19.*
    • unaffected 5.4.151 – ≤ 5.4.*
    • unaffected 5.10.71 – ≤ 5.10.*
    • unaffected 5.14.10 – ≤ 5.14.*
    • unaffected 5.15 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2021-47401 badge
[![CVE-2021-47401](https://cveledger.app/badge/CVE-2021-47401.svg)](https://cveledger.app/cve/CVE-2021-47401)

Record last updated .