CVE-2023-53198

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 2025-09-15. 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-2023-59778 (ENISA EUVD) · GHSA-hmqp-vg4p-vwv9 (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:

raw: Fix NULL deref in raw_get_next().

Dae R. Jeong reported a NULL deref in raw_get_next() [0].

It seems that the repro was running these sequences in parallel so that one thread was iterating on a socket that was being freed in another netns.

unshare(0x40060200) r0 = syz_open_procfs(0x0, &(0x7f0000002080)='net/raw\x00') socket$inet_icmp_raw(0x2, 0x3, 0x1) pread64(r0, &(0x7f0000000000)=""/10, 0xa, 0x10000000007f)

After commit 0daf07e52709 ("raw: convert raw sockets to RCU"), we use RCU and hlist_nulls_for_each_entry() to iterate over SOCK_RAW sockets. However, we should use spinlock for slow paths to avoid the NULL deref.

Also, SOCK_RAW does not use SLAB_TYPESAFE_BY_RCU, and the slab object is not reused during iteration in the grace period. In fact, the lockless readers do not check the nulls marker with get_nulls_value(). So, SOCK_RAW should use hlist instead of hlist_nulls.

Instead of adding an unnecessary barrier by sk_nulls_for_each_rcu(), let's convert hlist_nulls to hlist and use sk_for_each_rcu() for fast paths and sk_for_each() and spinlock for /proc/net/raw.

[0]: general protection fault, probably for non-canonical address 0xdffffc0000000005: 0000 [#1] PREEMPT SMP KASAN KASAN: null-ptr-deref in range [0x0000000000000028-0x000000000000002f] CPU: 2 PID: 20952 Comm: syz-executor.0 Not tainted 6.2.0-g048ec869bafd-dirty #7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 RIP: 0010:read_pnet include/net/net_namespace.h:383 [inline] RIP: 0010:sock_net include/net/sock.h:649 [inline] RIP: 0010:raw_get_next net/ipv4/raw.c:974 [inline] RIP: 0010:raw_get_idx net/ipv4/raw.c:986 [inline] RIP: 0010:raw_seq_start+0x431/0x800 net/ipv4/raw.c:995 Code: ef e8 33 3d 94 f7 49 8b 6d 00 4c 89 ef e8 b7 65 5f f7 49 89 ed 49 83 c5 98 0f 84 9a 00 00 00 48 83 c5 c8 48 89 e8 48 c1 e8 03 <42> 80 3c 30 00 74 08 48 89 ef e8 00 3d 94 f7 4c 8b 7d 00 48 89 ef RSP: 0018:ffffc9001154f9b0 EFLAGS: 00010206 RAX: 0000000000000005 RBX: 1ffff1100302c8fd RCX: 0000000000000000 RDX: 0000000000000028 RSI: ffffc9001154f988 RDI: ffffc9000f77a338 RBP: 0000000000000029 R08: ffffffff8a50ffb4 R09: fffffbfff24b6bd9 R10: fffffbfff24b6bd9 R11: 0000000000000000 R12: ffff88801db73b78 R13: fffffffffffffff9 R14: dffffc0000000000 R15: 0000000000000030 FS: 00007f843ae8e700(0000) GS:ffff888063700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000055bb9614b35f CR3: 000000003c672000 CR4: 00000000003506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: seq_read_iter+0x4c6/0x10f0 fs/seq_file.c:225 seq_read+0x224/0x320 fs/seq_file.c:162 pde_read fs/proc/inode.c:316 [inline] proc_reg_read+0x23f/0x330 fs/proc/inode.c:328 vfs_read+0x31e/0xd30 fs/read_write.c:468 ksys_pread64 fs/read_write.c:665 [inline] __do_sys_pread64 fs/read_write.c:675 [inline] __se_sys_pread64 fs/read_write.c:672 [inline] __x64_sys_pread64+0x1e9/0x280 fs/read_write.c:672 do_syscall_x64 arch/x86/entry/common.c:51 [inline] do_syscall_64+0x4e/0xa0 arch/x86/entry/common.c:82 entry_SYSCALL_64_after_hwframe+0x63/0xcd RIP: 0033:0x478d29 Code: f7 d8 64 89 02 b8 ff ff ff ff c3 66 0f 1f 44 00 00 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 bc ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007f843ae8dbe8 EFLAGS: 00000246 ORIG_RAX: 0000000000000011 RAX: ffffffffffffffda RBX: 0000000000791408 RCX: 0000000000478d29 RDX: 000000000000000a RSI: 0000000020000000 RDI: 0000000000000003 RBP: 00000000f477909a R08: 0000000000000000 R09: 0000000000000000 R10: 000010000000007f R11: 0000000000000246 R12: 0000000000791740 R13: 0000000000791414 R14: 0000000000791408 R15: 00007ffc2eb48a50 Modules linked in: ---[ end trace 0000000000000000 ]--- RIP: 0010 ---truncated---

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 BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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
4th
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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

September 15, 2025

Last Modified

December 2, 2025

References (3)

Vendor Advisories for CVE-2023-53198(1)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatkernel-0:5.14.0-362.8.1.el9_32023-11-07redhat
linuxKernel @ 6.1.24 (fixes >=6.0.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

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 36× 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 92 of 186 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. 8 repeat rows among the latest 100 are merged into the row they repeat. The 94 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-53198?
CVE-2023-53198 is a medium-severity vulnerability; its CVE record was published on September 15, 2025. In the Linux kernel, the following vulnerability has been resolved: raw: Fix NULL deref in raw_get_next(). Dae R. Jeong reported a NULL deref in raw_get_next() [0]. It seems that the repro was running these sequences in parallel so that one thread was iterating on a socket that was being freed in…
When was the CVE record for CVE-2023-53198 published?
The CVE record for CVE-2023-53198 was published on September 15, 2025. 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 December 2, 2025; the record at its source may have been updated since.
Is CVE-2023-53198 actively exploited?
CVE-2023-53198 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-53198?
CVE-2023-53198 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-53198?
A fix for CVE-2023-53198 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-53198 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-2023-53198

Explore →

Is Your Infrastructure Affected by CVE-2023-53198?

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

Book a Demo →Browse All CVEs