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-53167fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios

Description

In the Linux kernel, the following vulnerability has been resolved: fuse: limit FUSE_NOTIFY_RETRIEVE to uptodate folios FUSE_NOTIFY_RETRIEVE must be limited to uptodate folios; !uptodate folios can contain uninitialized data. Since FUSE_NOTIFY_RETRIEVE is intended to only return data that is already in the page cache and not wait for data from the FUSE daemon, treat !uptodate folios as if they weren't present. This only has security impact on systems that don't enable automatic zero-initialization of all page allocations via CONFIG_INIT_ON_ALLOC_DEFAULT_ON or init_on_alloc=1.

Timeline

  1. ID reserved

    By Linux

  2. · 16 days later

    Published

  3. · 4 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-2026-53167, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.13% · top 97% 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 5.5.

Affected products

  • Linux · Linux

    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < feafe8ccb1584254f59fbd4946d6ca7ef1e3e99c
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 651801d75ad0897dbd331b3cc6a4da3e78f60d42
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 4e14f29473eda18fb2af082dd2fd4c12139862cd
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 8bef2f840b43e0879478fe3aaa9ff2f0b80798a5
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 68a9282d5ea5b8780d59122505ad633e6daede90
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 56763afa013444a9d84ca1b74e4b7130942177ba
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 1fb8735a3a4d894f8c1f90b741a3ab1d3817f9bd
    • affected 2d45ba381a74a743eeaa2b06c7c5c0d2bf73ba1a – < 4e3d1b2c48ca6c55f1e9ca7f8dccc76f120f276c
  • Linux · Linux

    • affected 2.6.36
    • unaffected < 2.6.36
    • unaffected 5.10.260 – ≤ 5.10.*
    • unaffected 5.15.211 – ≤ 5.15.*
    • unaffected 6.1.177 – ≤ 6.1.*
    • unaffected 6.6.144 – ≤ 6.6.*
    • unaffected 6.12.95 – ≤ 6.12.*
    • unaffected 6.18.36 – ≤ 6.18.*
    • unaffected 7.0.13 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References10

Sources

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

Badge for a README or a ticket

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

Record last updated .