CVE-2023-52889

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 (severity: MODERATE) published 2024-08-17. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2023-59602 (ENISA EUVD) · GHSA-wfg9-r8xh-vw3h (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:

apparmor: Fix null pointer deref when receiving skb during sock creation

The panic below is observed when receiving ICMP packets with secmark set while an ICMP raw socket is being created. SK_CTX(sk)->label is updated in apparmor_socket_post_create(), but the packet is delivered to the socket before that, causing the null pointer dereference. Drop the packet if label context is not set.

BUG: kernel NULL pointer dereference, address: 000000000000004c #PF: supervisor read access in kernel mode #PF: error_code(0x0000) - not-present page PGD 0 P4D 0 Oops: 0000 [#1] PREEMPT SMP NOPTI CPU: 0 PID: 407 Comm: a.out Not tainted 6.4.12-arch1-1 #1 3e6fa2753a2d75925c34ecb78e22e85a65d083df Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 05/28/2020 RIP: 0010:aa_label_next_confined+0xb/0x40 Code: 00 00 48 89 ef e8 d5 25 0c 00 e9 66 ff ff ff 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 66 0f 1f 00 0f 1f 44 00 00 89 f0 <8b> 77 4c 39 c6 7e 1f 48 63 d0 48 8d 14 d7 eb 0b 83 c0 01 48 83 c2 RSP: 0018:ffffa92940003b08 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 000000000000000e RDX: ffffa92940003be8 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffff8b57471e7800 R08: ffff8b574c642400 R09: 0000000000000002 R10: ffffffffbd820eeb R11: ffffffffbeb7ff00 R12: ffff8b574c642400 R13: 0000000000000001 R14: 0000000000000001 R15: 0000000000000000 FS: 00007fb092ea7640(0000) GS:ffff8b577bc00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000000000004c CR3: 00000001020f2005 CR4: 00000000007706f0 PKRU: 55555554 Call Trace: ? __die+0x23/0x70 ? page_fault_oops+0x171/0x4e0 ? exc_page_fault+0x7f/0x180 ? asm_exc_page_fault+0x26/0x30 ? aa_label_next_confined+0xb/0x40 apparmor_secmark_check+0xec/0x330 security_sock_rcv_skb+0x35/0x50 sk_filter_trim_cap+0x47/0x250 sock_queue_rcv_skb_reason+0x20/0x60 raw_rcv+0x13c/0x210 raw_local_deliver+0x1f3/0x250 ip_protocol_deliver_rcu+0x4f/0x2f0 ip_local_deliver_finish+0x76/0xa0 __netif_receive_skb_one_core+0x89/0xa0 netif_receive_skb+0x119/0x170 ? __netdev_alloc_skb+0x3d/0x140 vmxnet3_rq_rx_complete+0xb23/0x1010 [vmxnet3 56a84f9c97178c57a43a24ec073b45a9d6f01f3a] vmxnet3_poll_rx_only+0x36/0xb0 [vmxnet3 56a84f9c97178c57a43a24ec073b45a9d6f01f3a] __napi_poll+0x28/0x1b0 net_rx_action+0x2a4/0x380 __do_softirq+0xd1/0x2c8 __irq_exit_rcu+0xbb/0xf0 common_interrupt+0x86/0xa0 asm_common_interrupt+0x26/0x40 RIP: 0010:apparmor_socket_post_create+0xb/0x200 Code: 08 48 85 ff 75 a1 eb b1 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 0f 1f 44 00 00 41 54 <55> 48 89 fd 53 45 85 c0 0f 84 b2 00 00 00 48 8b 1d 80 56 3f 02 48 RSP: 0018:ffffa92940ce7e50 EFLAGS: 00000286 RAX: ffffffffbc756440 RBX: 0000000000000000 RCX: 0000000000000001 RDX: 0000000000000003 RSI: 0000000000000002 RDI: ffff8b574eaab740 RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000 R10: ffff8b57444cec70 R11: 0000000000000000 R12: 0000000000000003 R13: 0000000000000002 R14: ffff8b574eaab740 R15: ffffffffbd8e4748 ? __pfx_apparmor_socket_post_create+0x10/0x10 security_socket_post_create+0x4b/0x80 __sock_create+0x176/0x1f0 __sys_socket+0x89/0x100 __x64_sys_socket+0x17/0x20 do_syscall_64+0x5d/0x90 ? do_syscall_64+0x6c/0x90 ? do_syscall_64+0x6c/0x90 ? do_syscall_64+0x6c/0x90 entry_SYSCALL_64_after_hwframe+0x72/0xdc

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
14th
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-11-07). 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

August 17, 2024

Last Modified

November 3, 2025

References (9)

Vendor Advisories for CVE-2023-52889(1)

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

Patch Availability(11)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.125.135~20.04.1) @ focal2026-10-24ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1072.72) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-lts-22.04 (5.15.0.1075.73) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-24.04 (6.8.0-50.51) @ noble2026-10-24ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1067.67) @ jammy2026-10-24ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k (6.8.0-1019.21.1) @ noble2026-10-24ubuntu
ubuntulinux-tools-gkeop-6.8 (6.8.0-1002.4) @ noble2026-10-24ubuntu
ubuntulinux-tools-azure-edge (6.8.0-1020.23~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-50.51~22.04.1) @ jammy2026-10-24ubuntu
ubuntulinux-tools-azure-edge (5.15.0.1078.87~20.04.1) @ focal2026-10-24ubuntu
linuxKernel @ 5.4.282 (fixes >=4.20.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

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
linux5.10.103-1 ... 5.10.92-2 (43 versions)
  • every version up to 5.10.226-1: fixed in 5.10.226-1
—
linux-6.16.1.106-3~deb11u1, 6.1.106-3~deb11u2, 6.1.106-3~deb11u3, 6.1.112-1~deb11u1
  • every version up to 6.1.119-1~deb11u1: fixed in 6.1.119-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.99-1 (26 versions)
  • every version up to 6.1.106-1: fixed in 6.1.106-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.3-1: fixed in 6.10.3-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.10.3-1: fixed in 6.10.3-1
—

Weakness Classification(1)

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

Additional Vendor Advisories

(10)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52889?
CVE-2023-52889 is a medium-severity vulnerability; its CVE record was published on August 17, 2024. In the Linux kernel, the following vulnerability has been resolved: apparmor: Fix null pointer deref when receiving skb during sock creation The panic below is observed when receiving ICMP packets with secmark set while an ICMP raw socket is being created. SK_CTX(sk)->label is updated in…
When was the CVE record for CVE-2023-52889 published?
The CVE record for CVE-2023-52889 was published on August 17, 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 November 3, 2025; the record at its source may have been updated since.
Is CVE-2023-52889 actively exploited?
CVE-2023-52889 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (14th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52889?
CVE-2023-52889 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2023-52889?
A fix for CVE-2023-52889 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-52889 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-52889

Explore →

Is Your Infrastructure Affected by CVE-2023-52889?

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

Book a Demo →Browse All CVEs