CVE-2024-35995

MEDIUMNVD 5.55.5

Also known asEUVD-2024-35713 (ENISA EUVD) · GHSA-4q6m-9fg8-7hvh (GitHub Security Advisories)Source: ENISA EUVD

5.5EG

EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).

Lower severity and no public exploit yet

CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 5.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

ACPI: CPPC: Use access_width over bit_width for system memory accesses

To align with ACPI 6.3+, since bit_width can be any 8-bit value, it cannot be depended on to be always on a clean 8b boundary. This was uncovered on the Cobalt 100 platform.

SError Interrupt on CPU26, code 0xbe000011 -- SError CPU: 26 PID: 1510 Comm: systemd-udevd Not tainted 5.15.2.1-13 #1 Hardware name: MICROSOFT CORPORATION, BIOS MICROSOFT CORPORATION pstate: 62400009 (nZCv daif +PAN -UAO +TCO -DIT -SSBS BTYPE=--) pc : cppc_get_perf_caps+0xec/0x410 lr : cppc_get_perf_caps+0xe8/0x410 sp : ffff8000155ab730 x29: ffff8000155ab730 x28: ffff0080139d0038 x27: ffff0080139d0078 x26: 0000000000000000 x25: ffff0080139d0058 x24: 00000000ffffffff x23: ffff0080139d0298 x22: ffff0080139d0278 x21: 0000000000000000 x20: ffff00802b251910 x19: ffff0080139d0000 x18: ffffffffffffffff x17: 0000000000000000 x16: ffffdc7e111bad04 x15: ffff00802b251008 x14: ffffffffffffffff x13: ffff013f1fd63300 x12: 0000000000000006 x11: ffffdc7e128f4420 x10: 0000000000000000 x9 : ffffdc7e111badec x8 : ffff00802b251980 x7 : 0000000000000000 x6 : ffff0080139d0028 x5 : 0000000000000000 x4 : ffff0080139d0018 x3 : 00000000ffffffff x2 : 0000000000000008 x1 : ffff8000155ab7a0 x0 : 0000000000000000 Kernel panic - not syncing: Asynchronous SError Interrupt CPU: 26 PID: 1510 Comm: systemd-udevd Not tainted 5.15.2.1-13 #1 Hardware name: MICROSOFT CORPORATION, BIOS MICROSOFT CORPORATION Call trace: dump_backtrace+0x0/0x1e0 show_stack+0x24/0x30 dump_stack_lvl+0x8c/0xb8 dump_stack+0x18/0x34 panic+0x16c/0x384 add_taint+0x0/0xc0 arm64_serror_panic+0x7c/0x90 arm64_is_fatal_ras_serror+0x34/0xa4 do_serror+0x50/0x6c el1h_64_error_handler+0x40/0x74 el1h_64_error+0x7c/0x80 cppc_get_perf_caps+0xec/0x410 cppc_cpufreq_cpu_init+0x74/0x400 [cppc_cpufreq] cpufreq_online+0x2dc/0xa30 cpufreq_add_dev+0xc0/0xd4 subsys_interface_register+0x134/0x14c cpufreq_register_driver+0x1b0/0x354 cppc_cpufreq_init+0x1a8/0x1000 [cppc_cpufreq] do_one_initcall+0x50/0x250 do_init_module+0x60/0x27c load_module+0x2300/0x2570 __do_sys_finit_module+0xa8/0x114 __arm64_sys_finit_module+0x2c/0x3c invoke_syscall+0x78/0x100 el0_svc_common.constprop.0+0x180/0x1a0 do_el0_svc+0x84/0xa0 el0_svc+0x2c/0xc0 el0t_64_sync_handler+0xa4/0x12c el0t_64_sync+0x1a4/0x1a8

Instead, use access_width to determine the size and use the offset and width to shift and mask the bits to read/write out. Make sure to add a check for system memory since pcc redefines the access_width to subspace id.

If access_width is not set, then fall back to using bit_width.

[ rjw: Subject and changelog edits, comment adjustments ]

CVSS v3: 5.5
EG Score: 5.5MEDIUMmedium confidence
EG Risk: 25
EPSS PROB: 0.2%
EPSS %ILE: 11th
KEV: Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.5): severity, escalated by confirmed exploitation. This CVE's 5.5 is its impact severity (EG Severity), not escalated.

EG Severity: 5.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood: 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-25). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation: None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority: SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 20, 2024

Last Modified

September 24, 2025

References (7)

CVE Programhttps://git.kernel.org/stable/c/01fc53be672acae37e611c80cc0b4f3939584de3Patch
CVE Programhttps://git.kernel.org/stable/c/1b890ae474d19800a6be1696df7fb4d9a41676e4Patch
CVE Programhttps://git.kernel.org/stable/c/2f4a4d63a193be6fd530d180bb13c3592052904cPatch
CVE Programhttps://git.kernel.org/stable/c/6cb6b12b78dcd8867a3fdbb1b6d0ed1df2b208d1Patch
CVE Programhttps://git.kernel.org/stable/c/4949affd5288b867cdf115f5b08d6166b2027f87Patch
CVE Programhttps://git.kernel.org/stable/c/6dfd79ed04c578f1d9a9a41ba5b2015cf9f03fc3Patch
CVE Programhttps://git.kernel.org/stable/c/b54c4632946ae42f2b39ed38abd909bbf78cbcc2Patch

Vendor Advisories for CVE-2024-35995(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 / Ecosystem	Fix (by version range) / Patch	Released	Source
redhat	kernel-0:5.14.0-503.11.1.el9_5	2024-11-12	redhat
linux	Kernel @ 6.1.90 (fixes >=4.9.0)	—	osv

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)

Package	Vulnerable range	Fix by version range	Dependents
linux	5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)	every version on: no fix on record	—

Debian:12(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	6.1.27-1 ... 6.1.90-1~bpo11+1 (21 versions)	every version up to 6.1.90-1: fixed in 6.1.90-1	—

Debian:13(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	—	every version up to 6.8.9-1: fixed in 6.8.9-1	—

Debian:14(1)

Package	Vulnerable range	Fix by version range	Dependents
linux	—	every version up to 6.8.9-1: fixed in 6.8.9-1	—

Data Freshness Timeline

(refreshed 7× in last 7d / 39× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 213 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 117 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

2026-11-01 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-25 17:09 UTCEG score recompute
2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-24 07:01 UTCEG score recompute
2026-10-24 07:01 UTCVendor advisory
2026-10-24 07:01 UTCGHSA enrichmentGHSA-4q6m-9fg8-7hvh · GitHub CVSS 5.5
2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-21 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-18 07:13 UTCEG score recompute
2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile

Show 71 more

2026-10-12 17:52 UTCEG score recompute
2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-11 21:17 UTCEG score recompute
2026-10-11 16:10 UTCEG score recompute
2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-10 23:22 UTCOSV refresh
2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-08 17:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-30 19:46 UTCEG score recompute
2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-28 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-26 00:23 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-22 14:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-21 20:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-21 11:49 UTCOSV refresh
2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-07 15:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-05 15:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-02 09:44 UTCOSV refresh
2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-09-01 04:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-30 19:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-30 01:20 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-26 14:44 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-20 22:53 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-16 08:20 UTCOSV refresh
2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
2026-08-04 15:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile

Same vendor

10 shown

redhat:RHSA-2024:9315

Frequently asked(5)

What is CVE-2024-35995?

CVE-2024-35995 is a medium-severity vulnerability; its CVE record was published on May 20, 2024. In the Linux kernel, the following vulnerability has been resolved: ACPI: CPPC: Use access_width over bit_width for system memory accesses To align with ACPI 6.3+, since bit_width can be any 8-bit value, it cannot be depended on to be always on a clean 8b boundary. This was uncovered on the Cobalt…

When was the CVE record for CVE-2024-35995 published?

The CVE record for CVE-2024-35995 was published on May 20, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 24, 2025; the record at its source may have been updated since.

Is CVE-2024-35995 actively exploited?

CVE-2024-35995 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (11th percentile of EPSS-scored CVEs).

What is the CVSS score of CVE-2024-35995?

CVE-2024-35995 has a CVSS v3 base score of 5.5 (NVD).

How do I remediate CVE-2024-35995?

A fix for CVE-2024-35995 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-35995 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-35995

Explore →

Is Your Infrastructure Affected by CVE-2024-35995?

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

Book a Demo →Browse All CVEs

CVE-2024-35995

📅 Published

🔄 Last Modified

🔗 References (7)

📣 Vendor Advisories for CVE-2024-35995(2)