CVE-2026-89723

CVE CVE-2026-89723EUVD EUVD-2026-76635Veröffentlicht 2026-09-11T19:46:35.000ZZuletzt geändert 2026-09-14T12:02:13.000ZCVSS 7.8

Was das Advisory beschreibt

In the Linux kernel, the following vulnerability has been resolved: nilfs2: fix slab-out-of-bounds in nilfs_direct_propagate after truncation Shuangpeng Bai reported that KASAN detected a slab-out-of-bounds error in nilfs_direct_propagate() during testing. Analysis revealed that after truncating a file, a node block immediately below the B-tree root was not deleted. Instead, it remained in the B-tree node cache in a dirty state. The log writer subsequently detected this block and incorrectly invoked nilfs_direct_propagate() on it, which is designed to handle only data blocks in direct mapping. B-tree nodes in the cache are managed by virtual block numbers, and their logical keys typically exceed the range expected by direct mapping. Consequently, processing such a node as a direct mapping entry triggers a slab-out-of-bounds access. The root cause is that when a B-tree mapping collapses into a direct mapping during truncation, an intermediate node block pointed to by the root node is left behind as garbage instead of being explicitly deleted. This resolves the issue by adding a nilfs_btree_discard() operation to delete the remaining intermediate node block during the conversion. A 'deform' flag is added to the bop_delete interface to explicitly signal that the deletion is part of a mapping transformation. This allows the B-tree mapping implementation to perform the necessary cleanup and discarding of the residual node structure that would be otherwise be left orphaned after the transition.

Quelle: EUVD (ENISA), im Wortlaut der Meldung.

Produkte, die das Advisory nennt

Diese Angaben stammen aus der Meldung selbst, nicht aus einer Prüfung durch uns.

• Linux — Linux 36a580eb489f54d81a0534974962e732a314b999 <bf49e6f6ddc12445a0330708b365de6458085980; 36a580eb489f54d81a0534974962e732a314b999 <4a1bb1f9f24a935c9b3f4fbf98012fa6d4ad826d; 36a580eb489f54d81a0534974962e732a314b999 <28362e8ce51377afdec1782e661e808328a10514; patch: 6.1.188; patch: 5.15.221; patch: 6.12.109; 36a580eb489f54d81a0534974962e732a314b999 <39005fd1ce654ffdecacddc406b9a038efe606e6; patch: 6.6.157; 36a580eb489f54d81a0534974962e732a314b999 <45662dedb8f272ef7f16e69f13424c4bd0399240; patch: 6.18.50; 36a580eb489f54d81a0534974962e732a314b999 <b313edfbc0c2a60f7ce09b2e81ee71909ab8ddaf; patch: 0; patch: 7.2.4; 2.6.30; 36a580eb489f54d81a0534974962e732a314b999 <5d3783c451a546373662ee11ec17019273e68034; patch: 5.10.270; 36a580eb489f54d81a0534974962e732a314b999 <448636c745a3f3b8582a0b8ce718c890a11c0fa9; patch: 7.3-rc1

Die genannten Versionen sind die Angabe der Meldung. Patchlage vergleicht keine Versionsnummern und leitet aus ihnen keine Aussage ab — welche Version installiert ist, muss ein Mensch nachsehen.

Im Produktkatalog geführt

Für diese Produkte kann ein Bestand in Patchlage erfasst werden. Ein Advisory dazu erscheint am Morgen danach im Lagebericht.

• Linux — Linux

Patchlage meldet Treffer und Verdachtsfälle. Zu allem anderen sagt dieses System nichts — weder diese Seite noch der Lagebericht behauptet je, dass ein Bestand sicher ist.