LiveActive security incident?Get immediate response
CVE Record

CVE-2024-47703: bpf, lsm: Add check for BPF LSM return value

In the Linux kernel, the following vulnerability has been resolved: bpf, lsm: Add check for BPF LSM return value A bpf prog returning a positive number attached to file_alloc_security hook makes kernel panic. This happens because file system can not filter out the positive number returned by the LSM prog using IS_ERR, and misinterprets this positive number as a file pointer. Given that hook file_alloc_security never returned positive number before the introduction of BPF LSM, and other BPF LSM hooks may encounter similar issues, this patch adds LSM return value check in verifier, to ensure no unexpected value is returned.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A locally executed BPF security program can return an unexpected positive value that Linux mistakes for a file pointer, causing a kernel panic. This can crash an affected host. The supplied record rates the issue 7.8 High, but the description directly demonstrates availability impact rather than data theft or modification.

Executive priority

Treat as a high-priority stability issue on shared, multi-user, or BPF-enabled Linux hosts. Patch through supported distribution channels after compatibility testing. Lower priority may be reasonable where local access and BPF program loading are strongly restricted, but confirm those controls rather than assuming protection.

Technical view

A BPF LSM program attached to file_alloc_security can return a positive integer. Filesystem code does not reject it through IS_ERR and may interpret it as a file pointer, triggering a kernel panic. The resolution adds verifier validation for BPF LSM return values to prevent unexpected positive results, with concern that other hooks could behave similarly.

Likely exposure

Exposure requires local, low-privilege access under the supplied CVSS vector and the ability to load and attach a BPF LSM program. Risk is greatest on shared or multi-user Linux systems where that capability is available. The supplied version data includes Linux 5.7, 6.10.13, 6.11.2, and 6.12, but is insufficient for precise distribution-level conclusions.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not marked as present in CISA KEV. Exploitation is local, requires low privileges according to the CVSS vector, needs no user interaction, and has low stated complexity. No remote attack path is described.

Researcher notes

The documented failure is improper return-value validation at the BPF LSM verifier boundary. A positive file_alloc_security result bypasses error-pointer handling and is consumed as a pointer. Although CVSS assigns high confidentiality, integrity, and availability impacts, the supplied narrative specifically substantiates kernel panic. Exact vulnerable ranges and backport coverage require vendor confirmation.

Mitigation direction

  • Apply a vendor-supported kernel update incorporating the cited BPF LSM verifier correction.
  • Check Linux distribution advisories for exact affected and fixed package versions.
  • Restrict untrusted users from loading or attaching BPF programs where operationally feasible.
  • Prioritize shared hosts where local users or workloads can access BPF LSM capabilities.

Validation and detection

  • Record running kernel and distribution package versions across Linux assets.
  • Compare each package against current distribution advisories for CVE-2024-47703.
  • Verify whether untrusted principals can load and attach BPF LSM programs.
  • Confirm the installed kernel includes the vendor backport or a cited corrective commit.
  • Review kernel panic records for events associated with BPF LSM activity.
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-2024-47703 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
1ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2024-47703Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux520b7aa00d8cd8e411ecc09f63a2acd90feb6d29, 520b7aa00d8cd8e411ecc09f63a2acd90feb6d29, 520b7aa00d8cd8e411ecc09f63a2acd90feb6d29unaffected
LinuxLinux5.7, 0, 6.10.13, 6.11.2, 6.12affected
Weakness

CWE details

No CWE listed

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