CVE-2026-90226

nfc: llcp: avoid userspace overflow on invalid optlen

N/A
Published: September 17, 2026 at 04:07 PM UTC
Updated: October 19, 2026 at 09:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: nfc: llcp: avoid userspace overflow on invalid optlen nfc_llcp_getsockopt() casts optval to (u32 __user *) for put_user(), so the kernel always stores 4 bytes regardless of the caller-supplied optlen. The existing min_t(u32, len, sizeof(u32)) only clamps the length reported back to userspace; it does not constrain the store. A call with optlen < 4 therefore writes past the user buffer, violating the getsockopt(2) contract for all five supported optnames. Reject any call with optlen < sizeof(u32) up front. 'len' is int, so a plain size comparison would promote a negative optlen to size_t and slip past the check; an explicit 'len < 0' test is added first to catch negative values before the size compare.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

26fd76cab2e61cedc5c25f7151fb31b57ddc53c73.10
Vendor states this is fixed in 35573c6cb081af2f4a7caeea291302aca5484526 (fixed)
Vendor states this is fixed in 42859562b7cc4313a84a584f338118edb7087066 (fixed)
Vendor states this is fixed in 598dcd53c52f8eeb9dd5382198c03960d5d40fcd (fixed)
Vendor states this is fixed in 7e40f2f5e7bc06c3ddef781180ce4f7994176547 (fixed)
Vendor states this is fixed in 8bf228fa02b1ed8ce622fb81fa8edc42be9aeb67 (fixed)
Vendor states this is fixed in 99985bfa8336fadcc69190ba2dcbd5386af3d661 (fixed)
Vendor states this is fixed in b4c5abaea06292e1dddb70eac1b51589b32c77a3 (fixed)
Vendor states this is fixed in bd6f1277b62bc1df348ca21739df2bc546fcd493 (fixed)
Vendor states this is fixed in 3.10 (unaffected)
Vendor states this is fixed in 5.10.270 (unaffected)
Vendor states this is fixed in 5.15.221 (unaffected)
Vendor states this is fixed in 6.1.188 (unaffected)
Vendor states this is fixed in 6.12.110 (unaffected)
Vendor states this is fixed in 6.18.52 (unaffected)
Vendor states this is fixed in 6.6.157 (unaffected)
Vendor states this is fixed in 7.2.6 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card