Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-90226nfc: llcp: avoid userspace overflow on invalid optlen

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (17 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < 42859562b7cc4313a84a584f338118edb7087066
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < 598dcd53c52f8eeb9dd5382198c03960d5d40fcd
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < 7e40f2f5e7bc06c3ddef781180ce4f7994176547
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < 35573c6cb081af2f4a7caeea291302aca5484526
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < b4c5abaea06292e1dddb70eac1b51589b32c77a3
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < 8bf228fa02b1ed8ce622fb81fa8edc42be9aeb67
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < bd6f1277b62bc1df348ca21739df2bc546fcd493
    • affected 26fd76cab2e61cedc5c25f7151fb31b57ddc53c7 – < 99985bfa8336fadcc69190ba2dcbd5386af3d661
  • Linux · Linux

    • affected 3.10
    • unaffected < 3.10
    • unaffected 5.10.270 – ≤ 5.10.*
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-90226 badge
[![CVE-2026-90226](https://cveledger.app/badge/CVE-2026-90226.svg)](https://cveledger.app/cve/CVE-2026-90226)

Record last updated .