CVE Catalog

CVE-2026-90226

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel NFC LLCP subsystem, nfc_llcp_getsockopt() always stores 4 bytes via put_user() regardless of the caller-supplied optlen. A call with optlen < 4 writes past the user buffer, violating the getsockopt(2) contract. The fix rejects calls with optlen < sizeof(u32), with an explicit check for negative values.

Risk Assessment

A local user could trigger a user-space buffer overflow, potentially leading to memory corruption in the application or privilege escalation. This requires access to an NFC LLCP socket.

Recommendation

Update the Linux kernel to a version containing the fix for CVE-2026-90226. Restrict access to NFC interfaces for unprivileged users.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS