CVE-2024-42111

MEDIUMNVD 6.36.3
EchelonGraph scoreMEDIUM confidence

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

Score 6.3 from GitHub Security Advisory published 2024-07-30. NVD baseline CVSS 6.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-39943 (ENISA EUVD) · GHSA-qg2w-5gv5-2cf4 (GitHub Security Advisories)Source: ENISA EUVD

6.3EG
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: 6.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

btrfs: always do the basic checks for btrfs_qgroup_inherit structure

[BUG] Syzbot reports the following regression detected by KASAN:

BUG: KASAN: slab-out-of-bounds in btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277 Read of size 8 at addr ffff88814628ca50 by task syz-executor318/5171

CPU: 0 PID: 5171 Comm: syz-executor318 Not tainted 6.10.0-rc2-syzkaller-00010-g2ab795141095 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/02/2024 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x241/0x360 lib/dump_stack.c:114 print_address_description mm/kasan/report.c:377 [inline] print_report+0x169/0x550 mm/kasan/report.c:488 kasan_report+0x143/0x180 mm/kasan/report.c:601 btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277 create_pending_snapshot+0x1359/0x29b0 fs/btrfs/transaction.c:1854 create_pending_snapshots+0x195/0x1d0 fs/btrfs/transaction.c:1922 btrfs_commit_transaction+0xf20/0x3740 fs/btrfs/transaction.c:2382 create_snapshot+0x6a1/0x9e0 fs/btrfs/ioctl.c:875 btrfs_mksubvol+0x58f/0x710 fs/btrfs/ioctl.c:1029 btrfs_mksnapshot+0xb5/0xf0 fs/btrfs/ioctl.c:1075 __btrfs_ioctl_snap_create+0x387/0x4b0 fs/btrfs/ioctl.c:1340 btrfs_ioctl_snap_create_v2+0x1f2/0x3a0 fs/btrfs/ioctl.c:1422 btrfs_ioctl+0x99e/0xc60 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:907 [inline] __se_sys_ioctl+0xfc/0x170 fs/ioctl.c:893 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fcbf1992509 RSP: 002b:00007fcbf1928218 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007fcbf1a1f618 RCX: 00007fcbf1992509 RDX: 0000000020000280 RSI: 0000000050009417 RDI: 0000000000000003 RBP: 00007fcbf1a1f610 R08: 00007ffea1298e97 R09: 0000000000000000 R10: 0000000000000000 R11: 0000000000000246 R12: 00007fcbf19eb660 R13: 00000000200002b8 R14: 00007fcbf19e60c0 R15: 0030656c69662f2e

And it also pinned it down to commit b5357cb268c4 ("btrfs: qgroup: do not check qgroup inherit if qgroup is disabled").

[CAUSE] That offending commit skips the whole qgroup inherit check if qgroup is not enabled.

But that also skips the very basic checks like num_ref_copies/num_excl_copies and the structure size checks.

Meaning if a qgroup enable/disable race is happening at the background, and we pass a btrfs_qgroup_inherit structure when the qgroup is disabled, the check would be completely skipped.

Then at the time of transaction commitment, qgroup is re-enabled and btrfs_qgroup_inherit() is going to use the incorrect structure and causing the above KASAN error.

[FIX] Make btrfs_qgroup_check_inherit() only skip the source qgroup checks. So that even if invalid btrfs_qgroup_inherit structure is passed in, we can still reject invalid ones no matter if qgroup is enabled or not.

Furthermore we do already have an extra safety inside btrfs_qgroup_inherit(), which would just ignore invalid qgroup sources, so even if we only skip the qgroup source check we're still safe.

CVSS v3
6.3
EG Score
6.3MEDIUMmedium confidence
EG Risk
28
EG Risk 28/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)
Severity63% × 45%
Impact severity (EG Severity): CVSS 6.3 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
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 (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.

EG Severity
6.3 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

July 30, 2024

Last Modified

August 5, 2026

References (2)

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-ibm-lts-24.04 (6.8.0-1014.14) @ noble2026-10-24ubuntu
ubuntulinux-tools-raspi (6.8.0-1014.16) @ noble2026-10-24ubuntu
ubuntulinux-tools-gke (6.8.0-1013.17) @ noble2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-48.48~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1017.20~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oracle-64k (6.8.0-1015.16) @ noble2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1017.19.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-48.48.3~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-oem-24.04a (6.8.0-1016.16) @ noble2026-10-24ubuntu
linuxKernel @ 6.9.9 (fixes >=6.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

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

Weakness Classification(1)

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

All Vendor Advisories

(10)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 212 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 116 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.2% · 11th percentile
  2. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  3. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  5. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  6. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  7. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  8. 2026-10-25 17:04 UTCEG score recompute
  9. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  10. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-24 05:29 UTCEG score recompute
  12. 2026-10-24 05:29 UTCVendor advisory
  13. 2026-10-24 05:28 UTCGHSA enrichmentGHSA-qg2w-5gv5-2cf4 · GitHub CVSS 6.3
  14. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-10-21 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-19 18:25 UTCOSV refresh
  19. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-18 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-18 07:05 UTCEG score recompute
  22. 2026-10-17 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  24. 2026-10-15 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  25. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
Show 71 more
  1. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-12 17:47 UTCEG score recompute
  3. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-11 21:13 UTCEG score recompute
  5. 2026-10-11 16:05 UTCEG score recompute
  6. 2026-10-11 13:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-08 17:08 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  13. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  16. 2026-09-30 19:51 UTCEG score recompute
  17. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-09-27 13:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-09-26 23:12 UTCOSV refresh
  22. 2026-09-26 15:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  23. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-09-22 14:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  26. 2026-09-21 20:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  27. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  28. 2026-09-19 15:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  29. 2026-09-18 19:26 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  30. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  31. 2026-09-16 05:12 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  32. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  33. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  34. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  35. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  36. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  37. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  38. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  39. 2026-09-07 08:48 UTCOSV refresh
  40. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  41. 2026-09-05 15:27 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  42. 2026-09-04 13:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  43. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  44. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  45. 2026-09-01 13:52 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  46. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  47. 2026-08-28 21:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  48. 2026-08-27 14:23 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  49. 2026-08-25 13:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  50. 2026-08-24 14:15 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  51. 2026-08-23 00:18 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  52. 2026-08-21 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  53. 2026-08-20 22:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  54. 2026-08-20 18:31 UTCOSV refresh
  55. 2026-08-19 17:02 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  56. 2026-08-18 13:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  57. 2026-08-17 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  58. 2026-08-16 14:54 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  59. 2026-08-16 02:13 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  60. 2026-08-15 01:28 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  61. 2026-08-13 21:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  62. 2026-08-12 13:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  63. 2026-08-11 13:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  64. 2026-08-10 23:58 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  65. 2026-08-09 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  66. 2026-08-08 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  67. 2026-08-07 16:25 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  68. 2026-08-06 13:45 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  69. 2026-08-05 19:16 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  70. 2026-08-05 12:06 UTCEG score recompute
  71. 2026-08-05 12:06 UTCVendor advisory

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-42111?
CVE-2024-42111 is a medium-severity vulnerability; its CVE record was published on July 30, 2024. In the Linux kernel, the following vulnerability has been resolved: btrfs: always do the basic checks for btrfs_qgroup_inherit structure [BUG] Syzbot reports the following regression detected by KASAN: BUG: KASAN: slab-out-of-bounds in btrfs_qgroup_inherit+0x42e/0x2e20 fs/btrfs/qgroup.c:3277 Read…
When was the CVE record for CVE-2024-42111 published?
The CVE record for CVE-2024-42111 was published on July 30, 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 August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-42111 actively exploited?
CVE-2024-42111 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-42111?
CVE-2024-42111 has a CVSS v3 base score of 6.3 (NVD).
How do I remediate CVE-2024-42111?
A fix for CVE-2024-42111 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-42111

Explore →

Is Your Infrastructure Affected by CVE-2024-42111?

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

Book a Demo →Browse All CVEs