LiveActive security incident?Get immediate response
CVE Record

CVE-2023-54247: bpf: Silence a warning in btf_type_id_size()

In the Linux kernel, the following vulnerability has been resolved: bpf: Silence a warning in btf_type_id_size() syzbot reported a warning in [1] with the following stacktrace: WARNING: CPU: 0 PID: 5005 at kernel/bpf/btf.c:1988 btf_type_id_size+0x2d9/0x9d0 kernel/bpf/btf.c:1988 ... RIP: 0010:btf_type_id_size+0x2d9/0x9d0 kernel/bpf/btf.c:1988 ... Call Trace: <TASK> map_check_btf kernel/bpf/syscall.c:1024 [inline] map_create+0x1157/0x1860 kernel/bpf/syscall.c:1198 __sys_bpf+0x127f/0x5420 kernel/bpf/syscall.c:5040 __do_sys_bpf kernel/bpf/syscall.c:5162 [inline] __se_sys_bpf kernel/bpf/syscall.c:5160 [inline] __x64_sys_bpf+0x79/0xc0 kernel/bpf/syscall.c:5160 do_syscall_x64 arch/x86/entry/common.c:50 [inline] do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80 entry_SYSCALL_64_after_hwframe+0x63/0xcd With the following btf [1] DECL_TAG 'a' type_id=4 component_idx=-1 [2] PTR '(anon)' type_id=0 [3] TYPE_TAG 'a' type_id=2 [4] VAR 'a' type_id=3, linkage=static and when the bpf_attr.btf_key_type_id = 1 (DECL_TAG), the following WARN_ON_ONCE in btf_type_id_size() is triggered: if (WARN_ON_ONCE(!btf_type_is_modifier(size_type) && !btf_type_is_var(size_type))) return NULL; Note that 'return NULL' is the correct behavior as we don't want a DECL_TAG type to be used as a btf_{key,value}_type_id even for the case like 'DECL_TAG -> STRUCT'. So there is no correctness issue here, we just want to silence warning. To silence the warning, I added DECL_TAG as one of kinds in btf_type_nosize() which will cause btf_type_id_size() returning NULL earlier without the warning. [1] https://lore.kernel.org/bpf/000000000000e0df8d05fc75ba86@google.com/

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel CVE describes a BPF/BTF input that can trigger an internal kernel warning. The source states the kernel already rejects the invalid type correctly and that there is no correctness issue. Business urgency appears low, but kernel version exposure should still be checked through vendor advisories.

Executive priority

Treat as a low-priority kernel hygiene item unless your vendor assigns higher severity. There is no cited active exploitation or correctness impact, but patch alignment should be handled through regular kernel update cycles.

Technical view

The issue is in btf_type_id_size() during BPF map creation when btf_key_type_id references a DECL_TAG. The expected result is NULL rejection, but a WARN_ON_ONCE fires before that path. The fix classifies DECL_TAG as a no-size BTF kind so rejection occurs earlier without warning.

Likely exposure

Exposure is limited to Linux systems running affected kernel versions with BPF functionality present. The bundle lists Linux as affected and provides stable kernel commits, but does not provide distro-specific package names or complete downstream backport status.

Exploitation context

The source cites syzbot discovery and a crafted BTF shape that triggers a warning. It does not cite active exploitation, KEV listing, privilege requirements, real-world abuse, or a demonstrated security impact beyond the warning.

Researcher notes

The important nuance is that the invalid DECL_TAG use is already rejected. The patch changes warning behavior, not acceptance logic. Evidence is insufficient to claim privilege escalation, memory corruption, denial of service, or exploitability.

Mitigation direction

  • Check Linux vendor advisories for patched kernel packages.
  • Map running kernels to the listed upstream stable fixes.
  • Prioritize normal kernel maintenance unless vendor guidance raises severity.
  • Track distro backports rather than relying only on upstream version numbers.

Validation and detection

  • Inventory Linux kernel versions across servers and container hosts.
  • Confirm whether vendor kernels include the referenced stable commits.
  • Review kernel logs for related BPF/BTF warning signatures.
  • Validate BPF exposure policy on multi-user or untrusted workload systems.
Prepared
Confidence
medium
Sources
5

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-54247 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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
4Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxb5ea834dde6b6e7f75e51d5f66dac8cd7c97b5ef, b5ea834dde6b6e7f75e51d5f66dac8cd7c97b5ef, b5ea834dde6b6e7f75e51d5f66dac8cd7c97b5efunaffected
LinuxLinux5.16, 0, 6.1.110, 6.4.7, 6.5affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.