CVE-2026-99514

Source
https://cve.org/CVERecord?id=CVE-2026-99514
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99514.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2026-99514
Downstream
Published
2026-11-19T14:44:14Z
Modified
2026-11-19T17:01:26Z
Summary
landlock: Fix superblock use-after-free in release_inode()
Details

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

landlock: Fix superblock use-after-free in release_inode()

Without this fix, release_inode() (task 1) can race with a umount operation in hook_sb_delete() (task 2). The order of operations in which the race occurs is:

  • task 2: hook_sb_delete() arrives at the end of the function, waiting for landlock_superblock(sb)->inode_refs to become zero.
  • task 1: release_inode(): does atomic_long_dec_and_test(), decrementing inode_refs to zero.
  • task 2: gets woken up through some other means, sees that inode_refs is zero and returns. The caller is the unmount operation and proceeds to release the superblock.
  • task 1: Runs wake_up_var(&landlock_superblock(sb)->inode_refs), dereferencing the sb_security on the freed-up superblock.

Notably, wake_up_var() does not dereference the pointer passed to it, and only uses it to determine an overapproximated set of tasks to wake up. So while it's potentially possible for an attacker to provide a different value for that pointer, this only results in the wrong set of tasks getting woken up, and in this scenario, no further tasks are actually waiting.

Nevertheless, KASAN detects it as a slab-use-after-free read on sb->s_security:

BUG: KASAN: slab-use-after-free in release_inode+0x196/0x290 Read of size 8 at addr ffff888103b6c0a8 by task repro/217 release_inode+0x196/0x290 landlock_put_object+0x71/0x90 landlock_free_rules+0x38/0xc0 landlock_put_ruleset+0x47/0x130 fop_ruleset_release+0x33/0x40 __fput+0x305/0x780 Freed by task 54: kfree+0x11c/0x390 process_scheduled_works+0x766/0xe50 worker_thread+0x7bc/0xb20

The fix is to determine &landlock_superblock(inode->i_sb)->inode_refs only once earlier in release_inode(), and later use that precalculated address for the wake_up_var() call, without having to dereference through the superblock.

Database specific
{
    "cna_assigner":  "Linux",
    "osv_generated_from":  "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/99xxx/CVE-2026-99514.json"
}
References

Affected packages

Git / git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git

Affected ranges

Type
GIT
Repo
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Events
Introduced
cb2c7d1a1776057c9a1f48ed1250d85e94d4850d
Fixed
1824d884e5076e3fdd83f44256746f2f95d062ec
Fixed
2b61008c9f884ead174a67f1cc70342a9efee3e4
Fixed
f79a0195db1f2568fd82999fd814af071b2dbca7
Fixed
3e271a27c46fd591d1011c7de5a644a41e2010f1

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99514.json"

Linux / Kernel

Package

Name
Kernel

Affected ranges

Type
ECOSYSTEM
Events
Introduced
5.13.0
Fixed
6.12.117
Type
ECOSYSTEM
Events
Introduced
6.13.0
Fixed
6.18.61
Type
ECOSYSTEM
Events
Introduced
6.19.0
Fixed
7.3.2

Database specific

source
"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-99514.json"