CVE-2023-52446

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-02-22. NVD baseline CVSS 7.8; sources differ by 0.0.

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

Also known asEUVD-2023-57071 (ENISA EUVD) · GHSA-3m37-qf9f-22vv (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

bpf: Fix a race condition between btf_put() and map_free()

When running ./test_progs -j in my local vm with latest kernel, I once hit a kasan error like below:

[ 1887.184724] BUG: KASAN: slab-use-after-free in bpf_rb_root_free+0x1f8/0x2b0 [ 1887.185599] Read of size 4 at addr ffff888106806910 by task kworker/u12:2/2830 [ 1887.186498] [ 1887.186712] CPU: 3 PID: 2830 Comm: kworker/u12:2 Tainted: G OEL 6.7.0-rc3-00699-g90679706d486-dirty #494 [ 1887.188034] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014 [ 1887.189618] Workqueue: events_unbound bpf_map_free_deferred [ 1887.190341] Call Trace: [ 1887.190666] [ 1887.190949] dump_stack_lvl+0xac/0xe0 [ 1887.191423] ? nf_tcp_handle_invalid+0x1b0/0x1b0 [ 1887.192019] ? panic+0x3c0/0x3c0 [ 1887.192449] print_report+0x14f/0x720 [ 1887.192930] ? preempt_count_sub+0x1c/0xd0 [ 1887.193459] ? __virt_addr_valid+0xac/0x120 [ 1887.194004] ? bpf_rb_root_free+0x1f8/0x2b0 [ 1887.194572] kasan_report+0xc3/0x100 [ 1887.195085] ? bpf_rb_root_free+0x1f8/0x2b0 [ 1887.195668] bpf_rb_root_free+0x1f8/0x2b0 [ 1887.196183] ? __bpf_obj_drop_impl+0xb0/0xb0 [ 1887.196736] ? preempt_count_sub+0x1c/0xd0 [ 1887.197270] ? preempt_count_sub+0x1c/0xd0 [ 1887.197802] ? _raw_spin_unlock+0x1f/0x40 [ 1887.198319] bpf_obj_free_fields+0x1d4/0x260 [ 1887.198883] array_map_free+0x1a3/0x260 [ 1887.199380] bpf_map_free_deferred+0x7b/0xe0 [ 1887.199943] process_scheduled_works+0x3a2/0x6c0 [ 1887.200549] worker_thread+0x633/0x890 [ 1887.201047] ? __kthread_parkme+0xd7/0xf0 [ 1887.201574] ? kthread+0x102/0x1d0 [ 1887.202020] kthread+0x1ab/0x1d0 [ 1887.202447] ? pr_cont_work+0x270/0x270 [ 1887.202954] ? kthread_blkcg+0x50/0x50 [ 1887.203444] ret_from_fork+0x34/0x50 [ 1887.203914] ? kthread_blkcg+0x50/0x50 [ 1887.204397] ret_from_fork_asm+0x11/0x20 [ 1887.204913] [ 1887.204913] [ 1887.205209] [ 1887.205416] Allocated by task 2197: [ 1887.205881] kasan_set_track+0x3f/0x60 [ 1887.206366] __kasan_kmalloc+0x6e/0x80 [ 1887.206856] __kmalloc+0xac/0x1a0 [ 1887.207293] btf_parse_fields+0xa15/0x1480 [ 1887.207836] btf_parse_struct_metas+0x566/0x670 [ 1887.208387] btf_new_fd+0x294/0x4d0 [ 1887.208851] __sys_bpf+0x4ba/0x600 [ 1887.209292] __x64_sys_bpf+0x41/0x50 [ 1887.209762] do_syscall_64+0x4c/0xf0 [ 1887.210222] entry_SYSCALL_64_after_hwframe+0x63/0x6b [ 1887.210868] [ 1887.211074] Freed by task 36: [ 1887.211460] kasan_set_track+0x3f/0x60 [ 1887.211951] kasan_save_free_info+0x28/0x40 [ 1887.212485] ____kasan_slab_free+0x101/0x180 [ 1887.213027] __kmem_cache_free+0xe4/0x210 [ 1887.213514] btf_free+0x5b/0x130 [ 1887.213918] rcu_core+0x638/0xcc0 [ 1887.214347] __do_softirq+0x114/0x37e

The error happens at bpf_rb_root_free+0x1f8/0x2b0:

00000000000034c0 : ; { 34c0: f3 0f 1e fa endbr64 34c4: e8 00 00 00 00 callq 0x34c9 34c9: 55 pushq %rbp 34ca: 48 89 e5 movq %rsp, %rbp ... ; if (rec && rec->refcount_off >= 0 && 36aa: 4d 85 ed testq %r13, %r13 36ad: 74 a9 je 0x3658 36af: 49 8d 7d 10 leaq 0x10(%r13), %rdi 36b3: e8 00 00 00 00 callq 0x36b8 <==== kasan function 36b8: 45 8b 7d 10 movl 0x10(%r13), %r15d <==== use-after-free load 36bc: 45 85 ff testl %r15d, %r15d 36bf: 78 8c js 0x364d

So the problem ---truncated---

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
13th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-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-27). 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 (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)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 Vulnrichment) · Technical impact total (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

February 22, 2024

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Sep 24, 2026
Patch available.
Web page

bpf: Fix a race condition between btf_put() and map_free() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f9ff6ef1c73cd9e1a6bb1ab3e57c5d141a536306
Web page

bpf: Fix a race condition between btf_put() and map_free() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d048dced8ea5eac6723ae873a40567e6f101ea42
Web page

bpf: Fix a race condition between btf_put() and map_free() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/59e5791f59dd83e8aa72a4e74217eabb6e8cfd90

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-10-28ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-10-28ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-10-28ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-10-28ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-10-28ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.41.41) @ mantic2026-10-28ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-10-28ubuntu
linuxKernel @ 6.6.14 (fixes >=6.2.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

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

Weakness Classification(1)

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

All Vendor Advisories

(8)

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52446?
CVE-2023-52446 is a high-severity vulnerability; its CVE record was published on February 22, 2024. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix a race condition between btf_put() and map_free() When running ./test_progs -j in my local vm with latest kernel, I once hit a kasan error like below: [ 1887.184724] BUG: KASAN: slab-use-after-free in…
When was the CVE record for CVE-2023-52446 published?
The CVE record for CVE-2023-52446 was published on February 22, 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 21, 2024; the record at its source may have been updated since.
Is CVE-2023-52446 actively exploited?
CVE-2023-52446 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (13th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-52446?
CVE-2023-52446 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52446?
A fix for CVE-2023-52446 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-2023-52446

Explore →

Is Your Infrastructure Affected by CVE-2023-52446?

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

Book a Demo →Browse All CVEs