Bug 2439854 (CVE-2026-23140) - CVE-2026-23140 kernel: bpf, test_run: Subtract size of xdp_frame from allowed metadata size
Summary: CVE-2026-23140 kernel: bpf, test_run: Subtract size of xdp_frame from allowed...
Keywords:
Status: NEW
Alias: CVE-2026-23140
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-14 16:01 UTC by OSIDB Bzimport
Modified: 2026-02-25 09:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-02-14 16:01:53 UTC
In the Linux kernel, the following vulnerability has been resolved:

bpf, test_run: Subtract size of xdp_frame from allowed metadata size

The xdp_frame structure takes up part of the XDP frame headroom,
limiting the size of the metadata. However, in bpf_test_run, we don't
take this into account, which makes it possible for userspace to supply
a metadata size that is too large (taking up the entire headroom).

If userspace supplies such a large metadata size in live packet mode,
the xdp_update_frame_from_buff() call in xdp_test_run_init_page() call
will fail, after which packet transmission proceeds with an
uninitialised frame structure, leading to the usual Bad Stuff.

The commit in the Fixes tag fixed a related bug where the second check
in xdp_update_frame_from_buff() could fail, but did not add any
additional constraints on the metadata size. Complete the fix by adding
an additional check on the metadata size. Reorder the checks slightly to
make the logic clearer and add a comment.

Comment 4 Helen Grace 2026-02-25 09:11:38 UTC
(In reply to Alexander B from comment #1)
> Upstream advisory:
> https://sprunki-retake.io/ https://lore.kernel.org/linux-cve-announce/2026021430-CVE-2026-23140-
> fed3@gregkh/T
Thanks for adding the upstream advisory and updating the classification. Medium severity seems appropriate given the potential for uninitialized frame usage in live packet mode.


Note You need to log in before you can comment on or make changes to this bug.