CVE-2024-26867

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3

Also known asEUVD-2024-24129 (ENISA EUVD) · GHSA-g62m-rg85-3mw3 (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:

comedi: comedi_8255: Correct error in subdevice initialization

The refactoring done in commit 5c57b1ccecc7 ("comedi: comedi_8255: Rework subdevice initialization functions") to the initialization of the io field of struct subdev_8255_private broke all cards using the drivers/comedi/drivers/comedi_8255.c module.

Prior to 5c57b1ccecc7, __subdev_8255_init() initialized the io field in the newly allocated struct subdev_8255_private to the non-NULL callback given to the function, otherwise it used a flag parameter to select between subdev_8255_mmio and subdev_8255_io. The refactoring removed that logic and the flag, as subdev_8255_mm_init() and subdev_8255_io_init() now explicitly pass subdev_8255_mmio and subdev_8255_io respectively to __subdev_8255_init(), only __subdev_8255_init() never sets spriv->io to the supplied callback. That spriv->io is NULL leads to a later BUG:

BUG: kernel NULL pointer dereference, address: 0000000000000000 PGD 0 P4D 0 Oops: 0010 [#1] SMP PTI CPU: 1 PID: 1210 Comm: systemd-udevd Not tainted 6.7.3-x86_64 #1 Hardware name: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffffa3f1c02d7b78 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff91f847aefd00 RCX: 000000000000009b RDX: 0000000000000003 RSI: 0000000000000001 RDI: ffff91f840f6fc00 RBP: ffff91f840f6fc00 R08: 0000000000000000 R09: 0000000000000001 R10: 0000000000000000 R11: 000000000000005f R12: 0000000000000000 R13: 0000000000000000 R14: ffffffffc0102498 R15: ffff91f847ce6ba8 FS: 00007f72f4e8f500(0000) GS:ffff91f8d5c80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 000000010540e000 CR4: 00000000000406f0 Call Trace: ? __die_body+0x15/0x57 ? page_fault_oops+0x2ef/0x33c ? insert_vmap_area.constprop.0+0xb6/0xd5 ? alloc_vmap_area+0x529/0x5ee ? exc_page_fault+0x15a/0x489 ? asm_exc_page_fault+0x22/0x30 __subdev_8255_init+0x79/0x8d [comedi_8255] pci_8255_auto_attach+0x11a/0x139 [8255_pci] comedi_auto_config+0xac/0x117 [comedi] ? __pfx___driver_attach+0x10/0x10 pci_device_probe+0x88/0xf9 really_probe+0x101/0x248 __driver_probe_device+0xbb/0xed driver_probe_device+0x1a/0x72 __driver_attach+0xd4/0xed bus_for_each_dev+0x76/0xb8 bus_add_driver+0xbe/0x1be driver_register+0x9a/0xd8 comedi_pci_driver_register+0x28/0x48 [comedi_pci] ? __pfx_pci_8255_driver_init+0x10/0x10 [8255_pci] do_one_initcall+0x72/0x183 do_init_module+0x5b/0x1e8 init_module_from_file+0x86/0xac __do_sys_finit_module+0x151/0x218 do_syscall_64+0x72/0xdb entry_SYSCALL_64_after_hwframe+0x6e/0x76 RIP: 0033:0x7f72f50a0cb9 Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 47 71 0c 00 f7 d8 64 89 01 48 RSP: 002b:00007ffd47e512d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139 RAX: ffffffffffffffda RBX: 0000562dd06ae070 RCX: 00007f72f50a0cb9 RDX: 0000000000000000 RSI: 00007f72f52d32df RDI: 000000000000000e RBP: 0000000000000000 R08: 00007f72f5168b20 R09: 0000000000000000 R10: 0000000000000050 R11: 0000000000000246 R12: 00007f72f52d32df R13: 0000000000020000 R14: 0000562dd06785c0 R15: 0000562dcfd0e9a8 Modules linked in: 8255_pci(+) comedi_8255 comedi_pci comedi intel_gtt e100(+) acpi_cpufreq rtc_cmos usbhid CR2: 0000000000000000 ---[ end trace 0000000000000000 ]--- RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffffa3f1c02d7b78 EFLAGS: 00010202 RAX: 0000000000000000 RBX: ffff91f847aefd00 RCX: 000000000000009b RDX: 0000000000000003 RSI: 0000000000000001 RDI: ffff91f840f6fc00 RBP: ffff91f840f6fc00 R08: 0000000000000000 R09: 0000000000000001 R10: 0000000000000000 R11: 000000000000005f R12: 0000000000000000 R13: 0000000000000000 R14: ffffffffc0102498 R15: ffff91f847ce6ba8 FS: ---truncated---

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity55% × 45%
Impact severity (EG Severity): CVSS 5.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
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.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
9th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
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

April 17, 2024

Last Modified

March 4, 2025

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 6.7.11 (fixes >=6.7.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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.7.12-1: fixed in 6.7.12-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 37× 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 97 of 208 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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 111 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-26867?
CVE-2024-26867 is a medium-severity vulnerability; its CVE record was published on April 17, 2024. In the Linux kernel, the following vulnerability has been resolved: comedi: comedi_8255: Correct error in subdevice initialization The refactoring done in commit 5c57b1ccecc7 ("comedi: comedi_8255: Rework subdevice initialization functions") to the initialization of the io field of struct…
When was the CVE record for CVE-2024-26867 published?
The CVE record for CVE-2024-26867 was published on April 17, 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 March 4, 2025; the record at its source may have been updated since.
Is CVE-2024-26867 actively exploited?
CVE-2024-26867 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-26867?
CVE-2024-26867 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2024-26867?
A fix for CVE-2024-26867 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2024-26867?

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