CVE-2021-47153

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

i2c: i801: Don't generate an interrupt on bus reset

Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt handler (i801_isr) is not prepared for this situation and will try to process the interrupt as if it was signaling the end of a successful transaction. In the case of a block transaction, this can result in an out-of-range memory access.

This condition was reproduced several times by syzbot: https://syzkaller.appspot.com/bug?extid=ed71512d469895b5b34e https://syzkaller.appspot.com/bug?extid=8c8dedc0ba9e03f6c79e https://syzkaller.appspot.com/bug?extid=c8ff0b6d6c73d81b610e https://syzkaller.appspot.com/bug?extid=33f6c360821c399d69eb https://syzkaller.appspot.com/bug?extid=be15dc0b1933f04b043a https://syzkaller.appspot.com/bug?extid=b4d3fd1dfd53e90afd79

So disable interrupts while trying to reset the bus. Interrupts will be enabled again for the following transaction.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
14%
KEV
Not listed

Published

March 25, 2024

Last Modified

August 5, 2026

Advisory Details (8)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e4d8716c3dcec47f1557024add24e1f3c09eb24b
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1f583d3813f204449037cd2acbfc09168171362a
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b523feb7e8e44652f92f3babb953a976e7ccbbef
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/04cc05e3716ae31b17ecdab7bc55c8170def1b8b
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c70e1ba2e7e65255a0ce004f531dd90dada97a8c
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dfa8929e117b0228a7765f5c3f5988a4a028f3c6
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/09c9e79f4c10cfb6b9e0e1b4dd355232e4b5a3b3
generic

i2c: i801: Don't generate an interrupt on bus reset - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9469082126cebb7337db3992d143f5e4edfe629

Vendor Advisories for CVE-2021-47153(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-rt-0:4.18.0-553.5.1.rt7.346.el8_102024-06-05redhat
redhatkernel-0:4.18.0-553.5.1.el8_102024-06-05redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux—5.10.46-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux—5.14.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 158 total refreshes for this CVE.

  1. 2026-09-18 19:24 UTCEPSS rescore
  2. 2026-09-17 19:23 UTCEPSS rescore
  3. 2026-09-16 14:05 UTCEPSS rescore
  4. 2026-09-16 14:05 UTCEPSS rescore
  5. 2026-09-15 03:06 UTCEPSS rescore
  6. 2026-09-12 14:57 UTCEPSS rescore
  7. 2026-09-11 14:49 UTCEPSS rescore
  8. 2026-09-11 09:33 UTCEPSS rescore
  9. 2026-09-08 21:57 UTCEPSS rescore
  10. 2026-09-07 15:58 UTCEPSS rescore
  11. 2026-09-07 05:47 UTCOSV refresh
  12. 2026-09-06 13:45 UTCEPSS rescore
  13. 2026-09-05 15:25 UTCEPSS rescore
  14. 2026-09-04 13:57 UTCEPSS rescore
  15. 2026-09-04 05:03 UTCEPSS rescore
  16. 2026-09-02 14:09 UTCEPSS rescore
  17. 2026-09-01 13:51 UTCEPSS rescore
  18. 2026-08-30 19:14 UTCEPSS rescore
  19. 2026-08-30 01:19 UTCEPSS rescore
  20. 2026-08-28 21:38 UTCEPSS rescore
  21. 2026-08-27 14:22 UTCEPSS rescore
  22. 2026-08-26 14:43 UTCEPSS rescore
  23. 2026-08-24 14:13 UTCEPSS rescore
  24. 2026-08-21 23:46 UTCEPSS rescore
  25. 2026-08-20 22:52 UTCEPSS rescore
Show 75 more
  1. 2026-08-20 15:31 UTCOSV refresh
  2. 2026-08-19 17:01 UTCEPSS rescore
  3. 2026-08-18 13:45 UTCEPSS rescore
  4. 2026-08-17 13:44 UTCEPSS rescore
  5. 2026-08-16 14:53 UTCEPSS rescore
  6. 2026-08-16 02:11 UTCEPSS rescore
  7. 2026-08-15 01:27 UTCEPSS rescore
  8. 2026-08-13 21:57 UTCEPSS rescore
  9. 2026-08-12 13:48 UTCEPSS rescore
  10. 2026-08-11 13:38 UTCEPSS rescore
  11. 2026-08-09 13:44 UTCEPSS rescore
  12. 2026-08-08 16:34 UTCEPSS rescore
  13. 2026-08-07 16:24 UTCEPSS rescore
  14. 2026-08-06 13:44 UTCEPSS rescore
  15. 2026-08-05 19:15 UTCEPSS rescore
  16. 2026-08-05 09:43 UTCEG score recompute
  17. 2026-08-05 09:43 UTCVendor advisory
  18. 2026-08-05 09:42 UTCGHSA enrichment
  19. 2026-08-04 15:06 UTCEPSS rescore
  20. 2026-08-04 12:20 UTCEG score recompute
  21. 2026-08-04 12:20 UTCVendor advisory
  22. 2026-08-04 12:20 UTCGHSA enrichment
  23. 2026-08-04 10:34 UTCEPSS rescore
  24. 2026-08-04 09:53 UTCEG score recompute
  25. 2026-08-04 09:53 UTCVendor advisory
  26. 2026-08-04 09:53 UTCGHSA enrichment
  27. 2026-08-03 10:33 UTCEPSS rescore
  28. 2026-08-02 02:24 UTCEPSS rescore
  29. 2026-08-01 09:06 UTCOSV refresh
  30. 2026-08-01 04:13 UTCEPSS rescore
  31. 2026-07-30 16:25 UTCEPSS rescore
  32. 2026-07-30 01:28 UTCEPSS rescore
  33. 2026-07-28 15:33 UTCEPSS rescore
  34. 2026-07-26 14:52 UTCEPSS rescore
  35. 2026-07-25 14:15 UTCEPSS rescore
  36. 2026-07-24 14:15 UTCEPSS rescore
  37. 2026-07-24 14:15 UTCEPSS rescore
  38. 2026-07-23 14:16 UTCEPSS rescore
  39. 2026-07-23 02:06 UTCEG score recompute
  40. 2026-07-22 22:52 UTCEG score recompute▲ 1.10
  41. 2026-07-22 14:06 UTCEPSS rescore
  42. 2026-07-21 15:22 UTCEPSS rescore
  43. 2026-07-21 15:22 UTCEPSS rescore
  44. 2026-07-20 17:05 UTCEPSS rescore
  45. 2026-07-19 14:29 UTCEPSS rescore
  46. 2026-07-19 02:27 UTCEPSS rescore
  47. 2026-07-19 02:27 UTCEPSS rescore
  48. 2026-07-18 10:02 UTCEPSS rescore
  49. 2026-07-16 17:00 UTCEPSS rescore
  50. 2026-07-16 17:00 UTCEPSS rescore
  51. 2026-07-15 16:55 UTCEPSS rescore
  52. 2026-07-15 01:58 UTCEPSS rescore
  53. 2026-07-15 01:58 UTCEPSS rescore
  54. 2026-07-14 16:10 UTCOSV refresh
  55. 2026-07-13 22:27 UTCEPSS rescore
  56. 2026-07-13 06:11 UTCEPSS rescore
  57. 2026-07-13 06:11 UTCEPSS rescore
  58. 2026-07-12 05:44 UTCEPSS rescore
  59. 2026-07-11 08:25 UTCEPSS rescore
  60. 2026-07-09 19:07 UTCEPSS rescore
  61. 2026-07-09 19:07 UTCEPSS rescore
  62. 2026-07-08 15:12 UTCEPSS rescore
  63. 2026-07-08 15:12 UTCEPSS rescore
  64. 2026-07-07 13:43 UTCEPSS rescore
  65. 2026-07-06 16:25 UTCEPSS rescore
  66. 2026-07-06 16:25 UTCEPSS rescore
  67. 2026-07-06 02:21 UTCEPSS rescore
  68. 2026-07-06 02:21 UTCEPSS rescore
  69. 2026-07-05 02:28 UTCEPSS rescore
  70. 2026-07-05 02:28 UTCEPSS rescore
  71. 2026-07-04 06:29 UTCEPSS rescore
  72. 2026-07-04 06:29 UTCEPSS rescore
  73. 2026-07-01 15:04 UTCEPSS rescore
  74. 2026-06-29 14:04 UTCEPSS rescore
  75. 2026-06-29 14:04 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2021-47153?
CVE-2021-47153 is a high vulnerability published on March 25, 2024. In the Linux kernel, the following vulnerability has been resolved: i2c: i801: Don't generate an interrupt on bus reset Now that the i2c-i801 driver supports interrupts, setting the KILL bit in a attempt to recover from a timed out transaction triggers an interrupt. Unfortunately, the interrupt…
When was CVE-2021-47153 disclosed?
CVE-2021-47153 was first published in the National Vulnerability Database on March 25, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2021-47153 actively exploited?
CVE-2021-47153 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.8% of all scored CVEs.
What is the CVSS score of CVE-2021-47153?
CVE-2021-47153 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2021-47153?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2021-47153, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2021-47153

Explore →

Is Your Infrastructure Affected by CVE-2021-47153?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs