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

Published Nov 19, 2026
·
Updated

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

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

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

task 2: hooksbdelete() arrives at the end of the function, waiting for landlocksuperblock(sb)->inoderefs to become zero. task 1: releaseinode(): does atomiclongdecandtest(), decrementing inoderefs to zero. task 2: gets woken up through some other means, sees that inoderefs is zero and returns. The caller is the unmount operation and proceeds to release the superblock. task 1: Runs wakeupvar(&landlocksuperblock(sb)->inoderefs), dereferencing the sbsecurity on the freed-up superblock.

Notably, wakeupvar() 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->ssecurity:

BUG: KASAN: slab-use-after-free in releaseinode+0x196/0x290 Read of size 8 at addr ffff888103b6c0a8 by task repro/217 releaseinode+0x196/0x290 landlockputobject+0x71/0x90 landlockfreerules+0x38/0xc0 landlockputruleset+0x47/0x130 foprulesetrelease+0x33/0x40 fput+0x305/0x780 Freed by task 54: kfree+0x11c/0x390 processscheduledworks+0x766/0xe50 workerthread+0x7bc/0xb20

The fix is to determine &landlocksuperblock(inode->isb)->inoderefs only once earlier in releaseinode(), and later use that precalculated address for the wakeupvar() call, without having to dereference through the superblock.

Affected Software

3 affected componentsFixes available
linux/kernel>=5.13.0<6.12.117
6.12.117
linux/kernel>=6.13.0<6.18.61
6.18.61
linux/kernel>=6.19.0<7.3.2
7.3.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.12.117
  2. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 6.18.61
  3. Upgrade

    Upgrade linux/Kernel to a version that resolves this vulnerability.

    Fixed in 7.3.2

Event History

Nov 19, 2026
CVE Published
via MITRE·02:44 PM
Data Sourced
via MITRE·02:44 PM
Description
Data Sourced
via OSV·02:44 PM
DescriptionAffected Software
Data Sourced
via NVD·03:18 PM
Description

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203