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-46953ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure

Description

In the Linux kernel, the following vulnerability has been resolved: ACPI: GTDT: Don't corrupt interrupt mappings on watchdow probe failure When failing the driver probe because of invalid firmware properties, the GTDT driver unmaps the interrupt that it mapped earlier. However, it never checks whether the mapping of the interrupt actially succeeded. Even more, should the firmware report an illegal interrupt number that overlaps with the GIC SGI range, this can result in an IPI being unmapped, and subsequent fireworks (as reported by Dann Frazier). Rework the driver to have a slightly saner behaviour and actually check whether the interrupt has been mapped before unmapping things.

Timeline

  1. ID reserved

    By Linux

  2. · 2 days later

    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-46953, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium6.7CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.24% · top 85% of all CVEs (18 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: Medium 6.7.

Affected products

  • Linux · Linux

    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < c3385a9122f8db15b453e07bfc88117fce7f3724
    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < 7b2162db1498c71962a4bb2f776fa4e76d4d305b
    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < 504632a3577a049dd9bb7aabae5b4476f9c586b4
    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < e0f2d86481eaa83df33b0793f75212919db7a19d
    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < 42e69521ee1fa5abf21f478d147d06bbfe6bf6a8
    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < 596e079c362ac17ed02aa1b99fdc444d62072a01
    • affected ca9ae5ec4ef0ed13833b03297ab319676965492c – < 1ecd5b129252249b9bc03d7645a7bda512747277
  • Linux · Linux

    • affected 4.12
    • unaffected < 4.12
    • unaffected 4.14.233 – ≤ 4.14.*
    • unaffected 4.19.191 – ≤ 4.19.*
    • unaffected 5.4.118 – ≤ 5.4.*
    • unaffected 5.10.36 – ≤ 5.10.*
    • unaffected 5.11.20 – ≤ 5.11.*
    • unaffected 5.12.3 – ≤ 5.12.*
    • unaffected 5.13 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .