CVE-2024-39467

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2024-06-25. 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:

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode()

syzbot reports a kernel bug as below:

F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ================================================================== BUG: KASAN: slab-out-of-bounds in f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] BUG: KASAN: slab-out-of-bounds in current_nat_addr fs/f2fs/node.h:213 [inline] BUG: KASAN: slab-out-of-bounds in f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 Read of size 1 at addr ffff88807a58c76c by task syz-executor280/5076

CPU: 1 PID: 5076 Comm: syz-executor280 Not tainted 6.9.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/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 f2fs_test_bit fs/f2fs/f2fs.h:2933 [inline] current_nat_addr fs/f2fs/node.h:213 [inline] f2fs_get_node_info+0xece/0x1200 fs/f2fs/node.c:600 f2fs_xattr_fiemap fs/f2fs/data.c:1848 [inline] f2fs_fiemap+0x55d/0x1ee0 fs/f2fs/data.c:1925 ioctl_fiemap fs/ioctl.c:220 [inline] do_vfs_ioctl+0x1c07/0x2e50 fs/ioctl.c:838 __do_sys_ioctl fs/ioctl.c:902 [inline] __se_sys_ioctl+0x81/0x170 fs/ioctl.c:890 do_syscall_x64 arch/x86/entry/common.c:52 [inline] do_syscall_64+0xf5/0x240 arch/x86/entry/common.c:83 entry_SYSCALL_64_after_hwframe+0x77/0x7f

The root cause is we missed to do sanity check on i_xattr_nid during f2fs_iget(), so that in fiemap() path, current_nat_addr() will access nat_bitmap w/ offset from invalid i_xattr_nid, result in triggering kasan bug report, fix it.

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
15%
KEV
Not listed

Published

June 25, 2024

Last Modified

August 5, 2026

Advisory Details (7)

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

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/20faaf30e55522bba2b56d9c46689233205d7717
generic

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/68e3cd4ecb8603936cccdc338929130045df2e57
generic

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

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

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1640dcf383cdba52be8b28d2a1a2aa7ef7a30c98
generic

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75c87e2ac6149abf44bdde0dd6d541763ddb0dff
generic

f2fs: fix to do sanity check on i_xattr_nid in sanity_check_inode() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c559a8d840562fbfce9f318448dda2f7d3e6d8e8

Patch Availability(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1013.14.1) @ noble2026-05-23ubuntu
ubuntulinux-tools-azure (6.8.0-1014.16) @ noble2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.4.0-1049 (5.4.0-1049.53) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-lts-20.04 (5.4.0.1129.122) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure-lts-20.04 (5.4.0.1135.129) @ focal2026-05-23ubuntu
ubuntulinux-virtual-hwe-24.04-edge (6.8.0-44.44) @ noble2026-05-23ubuntu
ubuntulinux-tools-bluefield (5.4.0.1090.86) @ focal2026-05-23ubuntu
ubuntulinux-tools-azure-edge (5.4.0.1135.142~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-tools-raspi-hwe-18.04-edge (5.4.0.1114.126~18.04.1) @ bionic2026-05-23ubuntu
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.121.121) @ jammy2026-05-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1013.14~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-22.04-edge (6.8.0-44.44.1~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1072.70) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1067.73~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-xilinx-zynqmp-tools-host (5.15.0-1035.39) @ jammy2026-05-23ubuntu
ubuntulinux-tools-raspi (6.8.0-1011.12) @ noble2026-05-23ubuntu
ubuntulinux-tools-lowlatency-hwe-20.04-edge (5.15.0.121.110) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-45.45~22.04.1) @ jammy2026-05-23ubuntu
ubuntulinux-tools-azure-fde-edge (5.15.0.1072.81~20.04.1.49) @ focal2026-05-23ubuntu
linuxKernel @ 5.4.278—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.

Weakness Classification(1)

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

All Vendor Advisories

(19)

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 11× in last 7d / 47× 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 124 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-39467?
CVE-2024-39467 is a high vulnerability published on June 25, 2024. In the Linux kernel, the following vulnerability has been resolved: f2fs: fix to do sanity check on ixattrnid in sanitycheckinode() syzbot reports a kernel bug as below: F2FS-fs (loop0): Mounted with checkpoint version = 48b305e4 ==================================================================…
When was CVE-2024-39467 disclosed?
CVE-2024-39467 was first published in the National Vulnerability Database on June 25, 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-39467 actively exploited?
CVE-2024-39467 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 85.1% of all scored CVEs.
What is the CVSS score of CVE-2024-39467?
CVE-2024-39467 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2024-39467?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-39467, 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-39467

Explore →

Is Your Infrastructure Affected by CVE-2024-39467?

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

Start Free Scan →Browse All CVEs