CVE-2023-54086: bpf: Add preempt_count_{sub,add} into btf id deny list
In the Linux kernel, the following vulnerability has been resolved:
bpf: Add preempt_count_{sub,add} into btf id deny list
The recursion check in __bpf_prog_enter* and __bpf_prog_exit*
leave preempt_count_{sub,add} unprotected. When attaching trampoline to
them we get panic as follows,
[ 867.843050] BUG: TASK stack guard page was hit at 0000000009d325cf (stack is 0000000046a46a15..00000000537e7b28)
[ 867.843064] stack guard page: 0000 [#1] PREEMPT SMP NOPTI
[ 867.843067] CPU: 8 PID: 11009 Comm: trace Kdump: loaded Not tainted 6.2.0+ #4
[ 867.843100] Call Trace:
[ 867.843101] <TASK>
[ 867.843104] asm_exc_int3+0x3a/0x40
[ 867.843108] RIP: 0010:preempt_count_sub+0x1/0xa0
[ 867.843135] __bpf_prog_enter_recur+0x17/0x90
[ 867.843148] bpf_trampoline_6442468108_0+0x2e/0x1000
[ 867.843154] ? preempt_count_sub+0x1/0xa0
[ 867.843157] preempt_count_sub+0x5/0xa0
[ 867.843159] ? migrate_enable+0xac/0xf0
[ 867.843164] __bpf_prog_exit_recur+0x2d/0x40
[ 867.843168] bpf_trampoline_6442468108_0+0x55/0x1000
...
[ 867.843788] preempt_count_sub+0x5/0xa0
[ 867.843793] ? migrate_enable+0xac/0xf0
[ 867.843829] __bpf_prog_exit_recur+0x2d/0x40
[ 867.843837] BUG: IRQ stack guard page was hit at 0000000099bd8228 (stack is 00000000b23e2bc4..000000006d95af35)
[ 867.843841] BUG: IRQ stack guard page was hit at 000000005ae07924 (stack is 00000000ffd69623..0000000014eb594c)
[ 867.843843] BUG: IRQ stack guard page was hit at 00000000028320f0 (stack is 00000000034b6438..0000000078d1bcec)
[ 867.843842] bpf_trampoline_6442468108_0+0x55/0x1000
...
That is because in __bpf_prog_exit_recur, the preempt_count_{sub,add} are
called after prog->active is decreased.
Fixing this by adding these two functions into btf ids deny list.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash a machine when BPF trampoline attachment reaches two preemption counter functions that were not protected by the recursion guard. The public record describes kernel panic and stack guard page hits, not data theft or privilege escalation. Business urgency depends on exposed systems that allow BPF tracing capabilities.
Executive priority
Treat this as a reliability and denial-of-service patching issue, not a confirmed breach indicator. Prioritize systems where local users, automation, or observability agents can exercise BPF features, and fold remaining servers into the next kernel maintenance window.
Technical view
The fix adds preempt_count_sub and preempt_count_add to the BTF ID deny list. Without that deny listing, attaching BPF trampolines to those functions can recurse through __bpf_prog_enter*/__bpf_prog_exit* handling after active state changes, causing stack guard page faults and kernel panic.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions where BPF trampoline attachment is possible. The source bundle lists Linux kernel versions including 5.13, 5.15.113, 6.1.30, 6.3.4, and 6.4 as affected, with fixed stable commits referenced.
Exploitation context
The bundle does not cite active exploitation, public exploit use, KEV listing, or remote attack paths. The described impact is a kernel panic triggered through BPF trampoline attachment, which typically makes this most relevant to systems where BPF use is available to local users or trusted workloads.
Researcher notes
Evidence is limited to the CVE record and upstream stable commit references. No CVSS, CWE, exploit status, or distro-specific fixed package data is provided. Validation should focus on kernel lineage, vendor backports, and whether the BTF deny-list change is present.
Mitigation direction
Apply a vendor kernel update containing the referenced stable fix commits.
Check Linux distribution advisories for exact fixed package versions.
Prioritize multi-tenant, developer, observability, and container hosts using eBPF.
If patching is delayed, follow vendor guidance for temporary BPF restrictions.
Avoid assuming unaffected status from upstream versions alone; verify downstream backports.
Validation and detection
Inventory running kernel versions across Linux fleets.
Confirm whether vendor packages include one of the referenced stable commits.
Check vulnerability scanner results after kernel update and reboot.
Review which hosts permit BPF tracing or trampoline attachment.
Document exceptions where vendor fixed builds are not yet available.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-54086 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Dec 24, 2025, 13:06 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.