CVE-2024-41000

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-07-12. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2024-39349 (ENISA EUVD) · GHSA-gfgx-m82f-4x3g (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

block/ioctl: prefer different overflow check

Running syzkaller with the newly reintroduced signed integer overflow sanitizer shows this report:

[ 62.982337] ------------[ cut here ]------------ [ 62.985692] cgroup: Invalid name [ 62.986211] UBSAN: signed-integer-overflow in ../block/ioctl.c:36:46 [ 62.989370] 9pnet_fd: p9_fd_create_tcp (7343): problem connecting socket to 127.0.0.1 [ 62.992992] 9223372036854775807 + 4095 cannot be represented in type 'long long' [ 62.997827] 9pnet_fd: p9_fd_create_tcp (7345): problem connecting socket to 127.0.0.1 [ 62.999369] random: crng reseeded on system resumption [ 63.000634] GUP no longer grows the stack in syz-executor.2 (7353): 20002000-20003000 (20001000) [ 63.000668] CPU: 0 PID: 7353 Comm: syz-executor.2 Not tainted 6.8.0-rc2-00035-gb3ef86b5a957 #1 [ 63.000677] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.16.3-debian-1.16.3-2 04/01/2014 [ 63.000682] Call Trace: [ 63.000686] [ 63.000731] dump_stack_lvl+0x93/0xd0 [ 63.000919] __get_user_pages+0x903/0xd30 [ 63.001030] __gup_longterm_locked+0x153e/0x1ba0 [ 63.001041] ? _raw_read_unlock_irqrestore+0x17/0x50 [ 63.001072] ? try_get_folio+0x29c/0x2d0 [ 63.001083] internal_get_user_pages_fast+0x1119/0x1530 [ 63.001109] iov_iter_extract_pages+0x23b/0x580 [ 63.001206] bio_iov_iter_get_pages+0x4de/0x1220 [ 63.001235] iomap_dio_bio_iter+0x9b6/0x1410 [ 63.001297] __iomap_dio_rw+0xab4/0x1810 [ 63.001316] iomap_dio_rw+0x45/0xa0 [ 63.001328] ext4_file_write_iter+0xdde/0x1390 [ 63.001372] vfs_write+0x599/0xbd0 [ 63.001394] ksys_write+0xc8/0x190 [ 63.001403] do_syscall_64+0xd4/0x1b0 [ 63.001421] ? arch_exit_to_user_mode_prepare+0x3a/0x60 [ 63.001479] entry_SYSCALL_64_after_hwframe+0x6f/0x77 [ 63.001535] RIP: 0033:0x7f7fd3ebf539 [ 63.001551] Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 14 00 00 90 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 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 [ 63.001562] RSP: 002b:00007f7fd32570c8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001 [ 63.001584] RAX: ffffffffffffffda RBX: 00007f7fd3ff3f80 RCX: 00007f7fd3ebf539 [ 63.001590] RDX: 4db6d1e4f7e43360 RSI: 0000000020000000 RDI: 0000000000000004 [ 63.001595] RBP: 00007f7fd3f1e496 R08: 0000000000000000 R09: 0000000000000000 [ 63.001599] R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000 [ 63.001604] R13: 0000000000000006 R14: 00007f7fd3ff3f80 R15: 00007ffd415ad2b8 ... [ 63.018142] ---[ end trace ]---

Historically, the signed integer overflow sanitizer did not work in the kernel due to its interaction with -fwrapv but this has since been changed [1] in the newest version of Clang; It was re-enabled in the kernel with Commit 557f8c582a9ba8ab ("ubsan: Reintroduce signed overflow sanitizer").

Let's rework this overflow checking logic to not actually perform an overflow during the check itself, thus avoiding the UBSAN splat.

[1]: https://github.com/llvm/llvm-project/pull/82432

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 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.3%
EPSS %ILE
22nd
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS. 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

July 12, 2024

Last Modified

October 15, 2026

Advisory Details (10)

Auto-updated Oct 15, 2026
Patch available.
Web pageMentions a patch (unverified)

[SECURITY] [DLA 4008-1] linux-6.1 security update

https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
Web page

block/ioctl: prefer different overflow check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ccb326b5f9e623eb7f130fbbf2505ec0e2dcaff9
Web page

block/ioctl: prefer different overflow check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/54160fb1db2de367485f21e30196c42f7ee0be4e
Web page

block/ioctl: prefer different overflow check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fd841ee01fb4a79cb7f5cc424b5c96c3a73b2d1e
Web page

block/ioctl: prefer different overflow check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/61ec76ec930709b7bcd69029ef1fe90491f20cf9
Web page

block/ioctl: prefer different overflow check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3220c90f4dbdc6d20d0608b164d964434a810d66
Web page

block/ioctl: prefer different overflow check - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/58706e482bf45c4db48b0c53aba2468c97adda24

Vendor Advisories for CVE-2024-41000(1)

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

Patch Availability(14)

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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (41 versions)
  • every version up to 5.10.221-1: fixed in 5.10.221-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.98-1 (25 versions)
  • every version up to 6.1.99-1: fixed in 6.1.99-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.7-1: fixed in 6.9.7-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.9.7-1: fixed in 6.9.7-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 9× in last 7d / 44× 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 234 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 138 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2024-41000?
CVE-2024-41000 is a high-severity vulnerability; its CVE record was published on July 12, 2024. In the Linux kernel, the following vulnerability has been resolved: block/ioctl: prefer different overflow check Running syzkaller with the newly reintroduced signed integer overflow sanitizer shows this report: [ 62.982337] ------------[ cut here ]------------ [ 62.985692] cgroup: Invalid name […
When was the CVE record for CVE-2024-41000 published?
The CVE record for CVE-2024-41000 was published on July 12, 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 October 15, 2026; the record at its source may have been updated since.
Is CVE-2024-41000 actively exploited?
CVE-2024-41000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-41000?
CVE-2024-41000 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-41000?
A fix for CVE-2024-41000 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-41000 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-41000

Explore →

Is Your Infrastructure Affected by CVE-2024-41000?

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