jfs: Verify inode mode when loading from disk
CVE-2025-40312 is fixed in 19 products on 1 platform, first by DEBIAN-CVE-2025-40312, released December 8, 2025. It is not reported as exploited. Patch Radar priority: High.
In the Linux kernel, the following vulnerability has been resolved: jfs: Verify inode mode when loading from disk The inode mode loaded from corrupted disk can be invalid. Do like what commit 0a9e74051313 ("isofs: Verify inode mode when loading from disk") does.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| dtb-aarch64 · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-64kb · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-64kb · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-azure · sles 15.7 | 6.4.0-150700.20.24.1 | SUSE-SU-2026:0281-1 | Jan 23, 2026 |
| kernel-debug · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-default-base · opensuse-leap 15.6 | 6.4.0-150600.23.84.1.150600.12.38.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default-base · sles 15.6 | 6.4.0-150600.23.84.1.150600.12.38.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-default-base · sles 15.7 | 6.4.0-150700.53.28.1.150700.17.19.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-docs · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-docs · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-docs · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-kvmsmall · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-livepatch-SLE15-SP6_Update_19 · sles 15.6 | 1-150600.13.3.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-livepatch-SLE15-SP7-RT_Update_8 · sles 15.7 | 1-150700.1.3.1 | SUSE-SU-2026:0278-1 | Jan 23, 2026 |
| kernel-livepatch-SLE15-SP7_Update_8 · sles 15.7 | 1-150700.15.3.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-obs-build · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-obs-build · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-obs-build · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-obs-qa · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-source · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-source · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-source · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-source-azure · sles 15.7 | 6.4.0-150700.20.24.1 | SUSE-SU-2026:0281-1 | Jan 23, 2026 |
| kernel-syms · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-syms · sles 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-syms · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| kernel-syms-azure · sles 15.7 | 6.4.0-150700.20.24.1 | SUSE-SU-2026:0281-1 | Jan 23, 2026 |
| kernel-zfcpdump · opensuse-leap 15.6 | 6.4.0-150600.23.84.1 | SUSE-SU-2026:0293-1 | Jan 26, 2026 |
| kernel-zfcpdump · sles 15.7 | 6.4.0-150700.53.28.1 | SUSE-SU-2026:0315-1 | Jan 28, 2026 |
| linux · Debian 12.15 (bookworm) | 6.1.159-1 | DEBIAN-CVE-2025-40312 | Dec 8, 2025 |
| linux · Debian 13.5 (trixie) | 6.12.63-1 | DEBIAN-CVE-2025-40312 | Dec 8, 2025 |
| linux · Debian 14 | 6.17.8-1 | DEBIAN-CVE-2025-40312 | Dec 8, 2025 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.