CVE-2024-38599

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-06-19. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

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

jffs2: prevent xattr node from overflowing the eraseblock

Add a check to make sure that the requested xattr node size is no larger than the eraseblock minus the cleanmarker.

Unlike the usual inode nodes, the xattr nodes aren't split into parts and spread across multiple eraseblocks, which means that a xattr node must not occupy more than one eraseblock. If the requested xattr value is too large, the xattr node can spill onto the next eraseblock, overwriting the nodes and causing errors such as:

jffs2: argh. node added in wrong place at 0x0000b050(2) jffs2: nextblock 0x0000a000, expected at 0000b00c jffs2: error: (823) do_verify_xattr_datum: node CRC failed at 0x01e050, read=0xfc892c93, calc=0x000000 jffs2: notice: (823) jffs2_get_inode_nodes: Node header CRC failed at 0x01e00c. {848f,2fc4,0fef511f,59a3d171} jffs2: Node at 0x0000000c with length 0x00001044 would run over the end of the erase block jffs2: Perhaps the file system was created with the wrong erase size? jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000010: 0x1044 instead

This breaks the filesystem and can lead to KASAN crashes such as:

BUG: KASAN: slab-out-of-bounds in jffs2_sum_add_kvec+0x125e/0x15d0 Read of size 4 at addr ffff88802c31e914 by task repro/830 CPU: 0 PID: 830 Comm: repro Not tainted 6.9.0-rc3+ #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.16.3-1-1 04/01/2014 Call Trace: dump_stack_lvl+0xc6/0x120 print_report+0xc4/0x620 ? __virt_addr_valid+0x308/0x5b0 kasan_report+0xc1/0xf0 ? jffs2_sum_add_kvec+0x125e/0x15d0 ? jffs2_sum_add_kvec+0x125e/0x15d0 jffs2_sum_add_kvec+0x125e/0x15d0 jffs2_flash_direct_writev+0xa8/0xd0 jffs2_flash_writev+0x9c9/0xef0 ? __x64_sys_setxattr+0xc4/0x160 ? do_syscall_64+0x69/0x140 ? entry_SYSCALL_64_after_hwframe+0x76/0x7e [...]

Found by Linux Verification Center (linuxtesting.org) with Syzkaller.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/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 computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

June 19, 2024

Last Modified

August 5, 2026

Advisory Details (9)

Auto-updated Aug 5, 2026
No patch confirmed yet.
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c6854e5a267c28300ff045480b5a7ee7f6f1d913
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/978a12c91b38bf1a213e567f3c20e2beef215f07
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8d431391320c5c5398ff966fb3a95e68a7def275
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/af82d8d2179b7277ad627c39e7e0778f1c86ccdb
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f06969df2e40ab1dc8f4364a5de967830c74a098
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a1d21bcd78cf4a4353e1e835789429c6b76aca8b
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f0eea095ce8c959b86e1e57fe36ca4fea5ae54f8
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/526235dffcac74c7823ed504dfac4f88d84ba5df
generic

jffs2: prevent xattr node from overflowing the eraseblock - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2904e1d9b64f72d291095e3cbb31634f08788b11

Patch Availability(17)

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.

Weakness Classification(1)

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

All Vendor Advisories

(16)

Data Freshness Timeline

(refreshed 12× in last 7d / 48× 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.

Showing the most recent 100 of 146 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2024-38599?
CVE-2024-38599 is a high vulnerability published on June 19, 2024. In the Linux kernel, the following vulnerability has been resolved: jffs2: prevent xattr node from overflowing the eraseblock Add a check to make sure that the requested xattr node size is no larger than the eraseblock minus the cleanmarker. Unlike the usual inode nodes, the xattr nodes aren't…
When was CVE-2024-38599 disclosed?
CVE-2024-38599 was first published in the National Vulnerability Database on June 19, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-38599 actively exploited?
CVE-2024-38599 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.2% of all scored CVEs.
What is the CVSS score of CVE-2024-38599?
CVE-2024-38599 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-38599?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-38599, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-38599

Explore →

Is Your Infrastructure Affected by CVE-2024-38599?

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