Skip to content
Fencer Intel
no cvss —

CVE-2026-99404 json

xfs: check fork type against dabtree block magic number

published 15h ago modified 14h ago also EUVD-2026-130063

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

In the Linux kernel, the following vulnerability has been resolved:

xfs: check fork type against dabtree block magic number

LOLLM complains that we fail to flag dabtree blocks that should never be associated with the file fork -- data forks can't point to xattr leaves, and attr forks can't point to dirent blocks. Add the missing checks.

Patch / fix

Is CVE-2026-99404 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected products

  • Linux Linux

Classification

Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.