An issue was discovered in the buffer queue driver in Samsung Automotive Processor Exynos Auto 8890, V7, V9, and V920. Lack of a length check leads to a Denial of Service in the kernel.
CVE-2024-53922
Score 5.7 from GitHub Security Advisory published 2026-09-14. a secondary CVSS source baseline 5.7; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.7
- EG Score
- 5.7(high)
- EG Risk
- 26(Track)EG Risk 26/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 computedSeverity57% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
September 13, 2026
Last Modified
September 14, 2026
Advisory Details (3)
Auto-updated Sep 14, 2026CVE-2024-53922 | Support | Samsung Semiconductor Global
https://semiconductor.samsung.com/support/quality-support/product-security-updates/cve-2024-53922/Bug Hunting im Linux-Kernel mit KASAN
https://diconium.com/de/blog/cybersecurity/hunting-bugs-in-linux-kernel-with-kasanProduct Security Update | Support | Samsung Semiconductor Global
https://semiconductor.samsung.com/support/quality-support/product-security-updates/Vendor Advisories for CVE-2024-53922(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 23× in last 7d / 23× 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.
- 2026-09-19 09:00 UTCEG score recompute
- 2026-09-19 09:00 UTCGHSA enrichment
- 2026-09-18 19:26 UTCEPSS rescore
- 2026-09-18 11:04 UTCEG score recompute
- 2026-09-18 11:04 UTCGHSA enrichment
- 2026-09-17 13:08 UTCGHSA enrichment
- 2026-09-16 15:13 UTCEG score recompute
- 2026-09-16 15:13 UTCGHSA enrichment
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 14:06 UTCEPSS rescore
- 2026-09-16 05:12 UTCEPSS rescore
- 2026-09-15 17:17 UTCEG score recompute
- 2026-09-15 17:17 UTCGHSA enrichment
- 2026-09-15 03:08 UTCEPSS rescore
- 2026-09-14 19:21 UTCEG score recompute
- 2026-09-14 19:21 UTCGHSA enrichment
- 2026-09-14 18:27 UTCEG score recompute
- 2026-09-14 18:27 UTCGHSA enrichment
- 2026-09-14 00:20 UTCEG score recompute
- 2026-09-13 23:50 UTCEG score recompute▲ 5.70
- 2026-09-13 23:49 UTCMITRE cvelistV5CVSS v3 → 5.7 · severity → MEDIUM
- 2026-09-13 23:45 UTCEG score recompute
- 2026-09-13 23:44 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2024-53922?
When was CVE-2024-53922 disclosed?
Is CVE-2024-53922 actively exploited?
What is the CVSS score of CVE-2024-53922?
How do I remediate CVE-2024-53922?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2024-53922
Is Your Infrastructure Affected by CVE-2024-53922?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.