CVE-2022-49007

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

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

Score 5.5 from GitHub Security Advisory published 2024-10-21. NVD baseline CVSS 5.5; sources differ by 0.0.

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

Also known asEUVD-2022-53891 (ENISA EUVD) · GHSA-9mmp-2f66-mf43 (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:

nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry()

Syzbot reported a null-ptr-deref bug:

NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds general protection fault, probably for non-canonical address 0xdffffc0000000002: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] CPU: 1 PID: 3603 Comm: segctord Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0 Hardware name: Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022 RIP: 0010:nilfs_palloc_commit_free_entry+0xe5/0x6b0 fs/nilfs2/alloc.c:608 Code: 00 00 00 00 fc ff df 80 3c 02 00 0f 85 cd 05 00 00 48 b8 00 00 00 00 00 fc ff df 4c 8b 73 08 49 8d 7e 10 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 26 05 00 00 49 8b 46 10 be a6 00 00 00 48 c7 c7 RSP: 0018:ffffc90003dff830 EFLAGS: 00010212 RAX: dffffc0000000000 RBX: ffff88802594e218 RCX: 000000000000000d RDX: 0000000000000002 RSI: 0000000000002000 RDI: 0000000000000010 RBP: ffff888071880222 R08: 0000000000000005 R09: 000000000000003f R10: 000000000000000d R11: 0000000000000000 R12: ffff888071880158 R13: ffff88802594e220 R14: 0000000000000000 R15: 0000000000000004 FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fb1c08316a8 CR3: 0000000018560000 CR4: 0000000000350ee0 Call Trace: nilfs_dat_commit_free fs/nilfs2/dat.c:114 [inline] nilfs_dat_commit_end+0x464/0x5f0 fs/nilfs2/dat.c:193 nilfs_dat_commit_update+0x26/0x40 fs/nilfs2/dat.c:236 nilfs_btree_commit_update_v+0x87/0x4a0 fs/nilfs2/btree.c:1940 nilfs_btree_commit_propagate_v fs/nilfs2/btree.c:2016 [inline] nilfs_btree_propagate_v fs/nilfs2/btree.c:2046 [inline] nilfs_btree_propagate+0xa00/0xd60 fs/nilfs2/btree.c:2088 nilfs_bmap_propagate+0x73/0x170 fs/nilfs2/bmap.c:337 nilfs_collect_file_data+0x45/0xd0 fs/nilfs2/segment.c:568 nilfs_segctor_apply_buffers+0x14a/0x470 fs/nilfs2/segment.c:1018 nilfs_segctor_scan_file+0x3f4/0x6f0 fs/nilfs2/segment.c:1067 nilfs_segctor_collect_blocks fs/nilfs2/segment.c:1197 [inline] nilfs_segctor_collect fs/nilfs2/segment.c:1503 [inline] nilfs_segctor_do_construct+0x12fc/0x6af0 fs/nilfs2/segment.c:2045 nilfs_segctor_construct+0x8e3/0xb30 fs/nilfs2/segment.c:2379 nilfs_segctor_thread_construct fs/nilfs2/segment.c:2487 [inline] nilfs_segctor_thread+0x3c3/0xf30 fs/nilfs2/segment.c:2570 kthread+0x2e4/0x3a0 kernel/kthread.c:376 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306 ...

If DAT metadata file is corrupted on disk, there is a case where req->pr_desc_bh is NULL and blocknr is 0 at nilfs_dat_commit_end() during a b-tree operation that cascadingly updates ancestor nodes of the b-tree, because nilfs_dat_commit_alloc() for a lower level block can initialize the blocknr on the same DAT entry between nilfs_dat_prepare_end() and nilfs_dat_commit_end().

If this happens, nilfs_dat_commit_end() calls nilfs_dat_commit_free() without valid buffer heads in req->pr_desc_bh and req->pr_bitmap_bh, and causes the NULL pointer dereference above in nilfs_palloc_commit_free_entry() function, which leads to a crash.

Fix this by adding a NULL check on req->pr_desc_bh and req->pr_bitmap_bh before nilfs_palloc_commit_free_entry() in nilfs_dat_commit_free().

This also calls nilfs_error() in that case to notify that there is a fatal flaw in the filesystem metadata and prevent further operations.

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
16th
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.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

October 21, 2024

Last Modified

October 25, 2024

References (8)

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
linuxKernel @ 4.9.335 (fixes >=2.6.30)—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

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (22 versions)
  • every version up to 5.10.158-1: fixed in 5.10.158-1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.12-1: fixed in 6.0.12-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.12-1: fixed in 6.0.12-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.0.12-1: fixed in 6.0.12-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× 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 197 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 100 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-49007?
CVE-2022-49007 is a medium-severity vulnerability; its CVE record was published on October 21, 2024. In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix NULL pointer dereference in nilfs_palloc_commit_free_entry() Syzbot reported a null-ptr-deref bug: NILFS (loop0): segctord starting. Construction interval = 5 seconds, CP frequency < 30 seconds general protection fault,…
When was the CVE record for CVE-2022-49007 published?
The CVE record for CVE-2022-49007 was published on October 21, 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 25, 2024; the record at its source may have been updated since.
Is CVE-2022-49007 actively exploited?
CVE-2022-49007 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (16th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-49007?
CVE-2022-49007 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2022-49007?
A fix for CVE-2022-49007 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-2022-49007

Explore →

Is Your Infrastructure Affected by CVE-2022-49007?

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

Book a Demo →Browse All CVEs