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-2025-38112net: Fix TOCTOU issue in sk_is_readable()

Description

In the Linux kernel, the following vulnerability has been resolved: net: Fix TOCTOU issue in sk_is_readable() sk->sk_prot->sock_is_readable is a valid function pointer when sk resides in a sockmap. After the last sk_psock_put() (which usually happens when socket is removed from sockmap), sk->sk_prot gets restored and sk->sk_prot->sock_is_readable becomes NULL. This makes sk_is_readable() racy, if the value of sk->sk_prot is reloaded after the initial check. Which in turn may lead to a null pointer dereference. Ensure the function pointer does not turn NULL after the check.

Timeline

  1. ID reserved

    By Linux

  2. · 3 months later

    Published

  3. · 16 months 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

CVSS scores of CVE-2025-38112, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium4.7CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.15% · top 96% of all CVEs (15 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < c2b26638476baee154920bb587fc94ff1bf04336
    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < 6fa68d7eab34d448a61aa24ea31e68b3231ed20d
    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < 8926a7ef1977a832dd6bf702f1a99303dbf15b15
    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < ff55c85a923e043d59d26b20a673a1b4a219c310
    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < 1e0de7582ceccbdbb227d4e0ddf65732f92526da
    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < 1b367ba2f94251822577daed031d6b9a9e11ba91
    • affected 8934ce2fd08171e8605f7fada91ee7619fe17ab8 – < 2660a544fdc0940bba15f70508a46cf9a6491230
  • Linux · Linux

    • affected 4.17
    • unaffected < 4.17
    • unaffected 5.10.239 – ≤ 5.10.*
    • unaffected 5.15.186 – ≤ 5.15.*
    • unaffected 6.1.142 – ≤ 6.1.*
    • unaffected 6.6.94 – ≤ 6.6.*
    • unaffected 6.12.34 – ≤ 6.12.*
    • unaffected 6.15.3 – ≤ 6.15.*
    • unaffected 6.16 – ≤ *

References

References9

Sources

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

Badge for a README or a ticket

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

Record last updated .