BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-31450High confidence

ext4: publish jinode after initialization

Linux · Linux

8.8HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 290 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.77% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Linux Linux and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 290 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

24 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 20 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.12.85-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.1.170-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcelinuxVendor fix publishedDebian records a fixed source-package version for this release.6.19.11-1Debian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinuxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-awsAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azureAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-fdeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-azure-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gcpAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-gkeopAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-ibmAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidiaAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-lowlatencyAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-nvidia-tegraAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oem-6.11Affected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-oracleAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspiAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-raspi-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-realtimeAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-riscvAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivelinux-xilinxAffected, no fix publishedCanonical OVAL identifies this running kernel flavour as affected and does not publish a fixed package version in this definition.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

4 current
CVE-2026-31450 · CSAF 2.0 · revision 20 · interimSUSE Product Security TeamCVE-2026-31450
288 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-macros as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-source as component of SUSE Linux Enterprise High Performance Computing 12 SP4
  • kernel-default as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-base as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-default-man as component of SUSE Linux Enterprise High Performance Computing 15 SP1
  • kernel-devel as component of SUSE Linux Enterprise High Performance Computing 15 SP1
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
SSA-019113 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-019113: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.6
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.6
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.6
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.6
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
CVE-2026-31450 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitykernel: ext4: publish jinode after initialization
260 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • kernel as a component of Red Hat Enterprise Linux 10
  • kernel-64k as a component of Red Hat Enterprise Linux 10
  • kernel-64k-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-devel-matched as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-core as a component of Red Hat Enterprise Linux 10
  • kernel-64k-debug-modules-extra as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel as a component of Red Hat Enterprise Linux 10
  • kernel-64k-devel-matched as a component of Red Hat Enterprise Linux 10
Summary
A race was found in ext4: `ext4_inode_attach_jinode()` published `ei->jinode` before `jbd2_journal_init_jbd_inode()` finished initializing it, so concurrent readers could observe a non-NULL journal inode whose `i_vfs_inode` was still NULL. The fast-commit flush path then called `jbd2_wait_inode_data()` and faulted on `i_mapping`. Upstream publishes the pointer only after full initialization using WRITE_ONCE/READ_ONCE and a write memory barrier.
Remediation
To mitigate this issue, prevent the ext4 module from being loaded. See https://access.redhat.com/solutions/41278 for instructions.
SSA-082556 · CSAF 2.0 · revision 7 · interimSiemens ProductCERTSSA-082556: Vulnerabilities in the additional GNU/Linux subsystem of the SIMATIC S7-1500 CPU 1518(F)-4 PN/DP MFP V3.1.5
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) >= V3.1.5
  • SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AC0) >= V3.1.5
  • SIPLUS S7-1500 CPU 1518-4 PN/DP MFP (6AG1518-4AX00-4AC0) >= V3.1.5
Summary
In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.
Remediation
Limit access to the interactive shell of the additional GNU/Linux subssytem to trusted personnel only.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-24788

No EUVD known-exploited evidence

In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f <49> 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
8.8 · CVSS 3.1
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 290 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f <49> 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f <49> 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

What

In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f <49> 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.

Why

The product dereferences a pointer that it expects to be valid but is NULL.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may disrupt the affected service.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → NULL Pointer Dereference → disrupt the affected service
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-476 ↗

CWE-476: NULL Pointer Dereference. The product dereferences a pointer that it expects to be valid but is NULL.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkDenial of serviceCWE-476
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2026-24788Official EUVD mapping

In the Linux kernel, the following vulnerability has been resolved: ext4: publish jinode after initialization ext4_inode_attach_jinode() publishes ei->jinode to concurrent users. It used to set ei->jinode before jbd2_journal_init_jbd_inode(), allowing a reader to observe a non-NULL jinode with i_vfs_inode still unset. The fast commit flush path can then pass this jinode to jbd2_wait_inode_data(), which dereferences i_vfs_inode->i_mapping and may crash. Below is the crash I observe: ``` BUG: unable to handle page fault for address: 000000010beb47f4 PGD 110e51067 P4D 110e51067 PUD 0 Oops: Oops: 0000 [#1] SMP NOPTI CPU: 1 UID: 0 PID: 4850 Comm: fc_fsync_bench_ Not tainted 6.18.0-00764-g795a690c06a5 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Arch Linux 1.17.0-2-2 04/01/2014 RIP: 0010:xas_find_marked+0x3d/0x2e0 Code: e0 03 48 83 f8 02 0f 84 f0 01 00 00 48 8b 47 08 48 89 c3 48 39 c6 0f 82 fd 01 00 00 48 85 c9 74 3d 48 83 f9 03 77 63 4c 8b 0f <49> 8b 71 08 48 c7 47 18 00 00 00 00 48 89 f1 83 e1 03 48 83 f9 02 RSP: 0018:ffffbbee806e7bf0 EFLAGS: 00010246 RAX: 000000000010beb4 RBX: 000000000010beb4 RCX: 0000000000000003 RDX: 0000000000000001 RSI: 0000002000300000 RDI: ffffbbee806e7c10 RBP: 0000000000000001 R08: 0000002000300000 R09: 000000010beb47ec R10: ffff9ea494590090 R11: 0000000000000000 R12: 0000002000300000 R13: ffffbbee806e7c90 R14: ffff9ea494513788 R15: ffffbbee806e7c88 FS: 00007fc2f9e3e6c0(0000) GS:ffff9ea6b1444000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000010beb47f4 CR3: 0000000119ac5000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> filemap_get_folios_tag+0x87/0x2a0 __filemap_fdatawait_range+0x5f/0xd0 ? srso_alias_return_thunk+0x5/0xfbef5 ? __schedule+0x3e7/0x10c0 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? cap_safe_nice+0x37/0x70 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 filemap_fdatawait_range_keep_errors+0x12/0x40 ext4_fc_commit+0x697/0x8b0 ? ext4_file_write_iter+0x64b/0x950 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ? srso_alias_return_thunk+0x5/0xfbef5 ? vfs_write+0x356/0x480 ? srso_alias_return_thunk+0x5/0xfbef5 ? preempt_count_sub+0x5f/0x80 ext4_sync_file+0xf7/0x370 do_fsync+0x3b/0x80 ? syscall_trace_enter+0x108/0x1d0 __x64_sys_fdatasync+0x16/0x20 do_syscall_64+0x62/0x2c0 entry_SYSCALL_64_after_hwframe+0x76/0x7e ... ``` Fix this by initializing the jbd2_inode first. Use smp_wmb() and WRITE_ONCE() to publish ei->jinode after initialization. Readers use READ_ONCE() to fetch the pointer.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1252Linux Kernel: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen, Sicherheitsmaßnahmen zu umgehen, Informationen offenzulegen, andere nicht näher spezifizierte Auswirkungen zu verursachen und möglicherweise Code auszuführen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260429Security Bulletin 29 Apr 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 29 Apr 2026, published on 29 April 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1229Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=CVE-2026-31424 Référence CVE CVE-2026-31425 https://www.cve.org/CVERecord?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1093Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31444 https://www.cve.org/CVERecord?id=CVE-2026-31444 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1066Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31434 Référence CVE CVE-2026-31438 https://www.cve.org/CVERecord?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1029Multiples vulnérabilités dans le noyau Linux de SUSE

rd?id=CVE-2023-2058 Référence CVE CVE-2023-53995 https://www.cve.org/CVERecord?id=CVE-2023-53995 Référence CVE CVE-2024-38542 https://www.cve.org/CVERecord?id=CVE-2024-38542 Référence CVE CVE-2025-21710 https://www.cve.org/CVERecord?id=CVE-2025-21710 Référence CVE CVE-2025-21953 https://www.cve.org/CVERecord?id=CVE-2025-21953 Référence CVE CVE-2025-38250 https://www.cve.org/CVERecord?id=CVE-2025-38250 Référence CVE CVE-2025-54518 https://www.cve.org/CVERecord?id=CVE-2025-54518 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31482 https://www.cve.org/CVERecord?id=CVE-2026-31482 Référence CVE CVE-2026-31483 https://www.cve.org/CVERecord?id=CVE-2026-31483 Référence CVE CVE-2026-31510 https://www.cve.org/CVERecord?id=CVE-2026-31510 Référence CVE CVE-2026-31542 https://www.cve.org/CVERecord?id=CVE-2026-31542 Référence CVE CVE-2026-31598 https://www.cve.org/CVERecord?id=CVE-2026-31598 Référence CVE CVE-2026-31624 https://www.cve.org/CVERecord?id=CVE-2026-31624 Référence CVE CVE-2026-31628 https://www.cve.org/CVERecord?id=CVE-2026-31628 Référence CVE CVE-2026-31678 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0985Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31422 Référence CVE CVE-2026-31423 https://www.cve.org/CVERecord?id=CVE-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=CVE-2026-31424 Référence CVE CVE-2026-31425 https://www.cve.org/CVERecord?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0956Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2025-71089 Référence CVE CVE-2026-23240 https://www.cve.org/CVERecord?id=CVE-2026-23240 Référence CVE CVE-2026-23248 https://www.cve.org/CVERecord?id=CVE-2026-23248 Référence CVE CVE-2026-23393 https://www.cve.org/CVERecord?id=CVE-2026-23393 Référence CVE CVE-2026-23394 https://www.cve.org/CVERecord?id=CVE-2026-23394 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31438 https://www.cve.org/CVERecord?id=CVE-2026-31438 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=CVE-2026-31495 Référence CVE CVE-2026-31499 https://www.cve.org/CVERecord?id=CVE-2026-31499 Référence CVE CVE-2026-31502 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0954Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31444 https://www.cve.org/CVERecord?id=CVE-2026-31444 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0927Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-23451 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31430 https://www.cve.org/CVERecord?id=CVE-2026-31430 Référence CVE CVE-2026-31438 https://www.cve.org/CVERecord?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31474 https://www.cve.org/CVERecord?id=CVE-2026-31474 Référence CVE CVE-2026-31479 https://www.cve.org/CVERecord?id=CVE-2026-31479 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31492 https://www.cve.org/CVERecord?id=CVE-2026-31492 Référence CVE CVE-2026-31495 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0926Multiples vulnérabilités dans le noyau Linux d'Ubuntu

d?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31444 https://www.cve.org/CVERecord?id=CVE-2026-31444 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0880Multiples vulnérabilités dans les produits Siemens

26-23398, CVE-2026-23414, CVE-2026-23422, CVE-2026-23434, CVE-2026-23438, CVE-2026-23439, CVE-2026-23446, CVE-2026-23449, CVE-2026-23450, CVE-2026-23452, CVE-2026-23454, CVE-2026-23455, CVE-2026-23456, CVE-2026-23457, CVE-2026-23458, CVE-2026-23463, CVE-2026-23474, CVE-2026-23475, CVE-2026-27135, CVE-2026-31389, CVE-2026-31391, CVE-2026-31396, CVE-2026-31402, CVE-2026-31403, CVE-2026-31411, CVE-2026-31414, CVE-2026-31415, CVE-2026-31416, CVE-2026-31417, CVE-2026-31418, CVE-2026-31421, CVE-2026-31422, CVE-2026-31423, CVE-2026-31424, CVE-2026-31427, CVE-2026-31428, CVE-2026-31431, CVE-2026-31441, CVE-2026-31446, CVE-2026-31447, CVE-2026-31448, CVE-2026-31450, CVE-2026-31452, CVE-2026-31466, CVE-2026-31469, CVE-2026-31485, CVE-2026-31494, CVE-2026-31495, CVE-2026-31496, CVE-2026-31503, CVE-2026-31504, CVE-2026-31507, CVE-2026-31508, CVE-2026-31515, CVE-2026-31518, CVE-2026-31521, CVE-2026-31533, CVE-2026-31546, CVE-2026-31555, CVE-2026-31563, CVE-2026-31565, CVE-2026-31628, CVE-2026-31634, CVE-2026-31649, CVE-2026-31651, CVE-2026-31658, CVE-2026-31664, CVE-2026-31665, CVE-2026-31669, CVE-2026-31670, CVE-2026-31671, CVE-2026-31674, CVE-2026-31680, CVE-2026-31682, CVE-2026-31737, CVE-2026-31752, CVE-2026-31761, CVE-2026-31768, CVE-2026-40355, CVE-2026-41989, CVE-2026-43011, CVE-2026-43024, CVE-2026

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0864Multiples vulnérabilités dans le noyau Linux de SUSE

d?id=CVE-2026-23438 Référence CVE CVE-2026-23444 https://www.cve.org/CVERecord?id=CVE-2026-23444 Référence CVE CVE-2026-23451 https://www.cve.org/CVERecord?id=CVE-2026-23451 Référence CVE CVE-2026-31396 https://www.cve.org/CVERecord?id=CVE-2026-31396 Référence CVE CVE-2026-31402 https://www.cve.org/CVERecord?id=CVE-2026-31402 Référence CVE CVE-2026-31414 https://www.cve.org/CVERecord?id=CVE-2026-31414 Référence CVE CVE-2026-31429 https://www.cve.org/CVERecord?id=CVE-2026-31429 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0696Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31418 Référence CVE CVE-2026-31421 https://www.cve.org/CVERecord?id=CVE-2026-31421 Référence CVE CVE-2026-31422 https://www.cve.org/CVERecord?id=CVE-2026-31422 Référence CVE CVE-2026-31423 https://www.cve.org/CVERecord?id=CVE-2026-31423 Référence CVE CVE-2026-31424 https://www.cve.org/CVERecord?id=CVE-2026-31424 Référence CVE CVE-2026-31425 https://www.cve.org/CVERecord?id=CVE-2026-31425 Référence CVE CVE-2026-31427 https://www.cve.org/CVERecord?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=CVE-2026-31469 Référence CVE CVE-2026-31473 https://www.cve.org/CVERecord?id=CVE-2026-31473 Référence CVE CVE-2026-31485 https://www.cve.org/CVERecord?id=CVE-2026-31485 Référence CVE CVE-2026-31494 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0547Multiples vulnérabilités dans le noyau Linux de Debian LTS

d?id=CVE-2026-31427 Référence CVE CVE-2026-31428 https://www.cve.org/CVERecord?id=CVE-2026-31428 Référence CVE CVE-2026-31431 https://www.cve.org/CVERecord?id=CVE-2026-31431 Référence CVE CVE-2026-31433 https://www.cve.org/CVERecord?id=CVE-2026-31433 Référence CVE CVE-2026-31434 https://www.cve.org/CVERecord?id=CVE-2026-31434 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=CVE-2026-31464 Référence CVE CVE-2026-31466 https://www.cve.org/CVERecord?id=CVE-2026-31466 Référence CVE CVE-2026-31467 https://www.cve.org/CVERecord?id=CVE-2026-31467 Référence CVE CVE-2026-31469 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0548Multiples vulnérabilités dans le noyau Linux de Debian

d?id=CVE-2026-31436 Référence CVE CVE-2026-31438 https://www.cve.org/CVERecord?id=CVE-2026-31438 Référence CVE CVE-2026-31439 https://www.cve.org/CVERecord?id=CVE-2026-31439 Référence CVE CVE-2026-31440 https://www.cve.org/CVERecord?id=CVE-2026-31440 Référence CVE CVE-2026-31441 https://www.cve.org/CVERecord?id=CVE-2026-31441 Référence CVE CVE-2026-31446 https://www.cve.org/CVERecord?id=CVE-2026-31446 Référence CVE CVE-2026-31447 https://www.cve.org/CVERecord?id=CVE-2026-31447 Référence CVE CVE-2026-31448 https://www.cve.org/CVERecord?id=CVE-2026-31448 Référence CVE CVE-2026-31449 https://www.cve.org/CVERecord?id=CVE-2026-31449 Référence CVE CVE-2026-31450 https://www.cve.org/CVERecord?id=CVE-2026-31450 Référence CVE CVE-2026-31451 https://www.cve.org/CVERecord?id=CVE-2026-31451 Référence CVE CVE-2026-31452 https://www.cve.org/CVERecord?id=CVE-2026-31452 Référence CVE CVE-2026-31453 https://www.cve.org/CVERecord?id=CVE-2026-31453 Référence CVE CVE-2026-31454 https://www.cve.org/CVERecord?id=CVE-2026-31454 Référence CVE CVE-2026-31455 https://www.cve.org/CVERecord?id=CVE-2026-31455 Référence CVE CVE-2026-31458 https://www.cve.org/CVERecord?id=CVE-2026-31458 Référence CVE CVE-2026-31462 https://www.cve.org/CVERecord?id=CVE-2026-31462 Référence CVE CVE-2026-31464 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0519Multiples vulnérabilités dans Microsoft Azure Linux

ence CERTFR-2026-AVI-0519 Titre Multiples vulnérabilités dans Microsoft Azure Linux Date de la première version 30 avril 2026 Date de la dernière version 30 avril 2026 Source(s) Bulletin de sécurité Microsoft CVE-2026-27820 du 18 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31439 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31441 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31444 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31446 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31447 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31448 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31450 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31451 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31452 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31453 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31454 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31455 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31458 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31467 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31469 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31473 du 23 avril 2026 Bulletin de sécurité Microsoft CVE-2026-31474 du 23 avril 2026 Bu

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014404LinuxのLinux KernelにおけるNULL ポインタデリファレンスに関する脆弱性

Linuxカーネルのext4ファイルシステムにおいて、初期化後にjinodeが公開されることでクラッシュを引き起こす脆弱性が修正されました。ext4_inode_attach_jinode()は並行アクセスするユーザーにei-jinodeを公開しており、これによりi_vfs_inodeが未設定の非NULLのjinodeを読み取っていました。その結果、jbd2_wait_inode_data()でi_vfs_inode-i_mappingを参照し、クラッシュが発生する可能性がありました。この問題はjbd2_inodeを先に初期化し、適切なメモリ障壁とWRITE_ONCE()を使ってei-jinodeを公開し、読み取り側はREAD_ONCE()で安全にポインタを取得するように修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Linux: < 3.11, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.134 ≤ 6.6.*, 6.12.81 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 22 Apr 2026 · Last source change 8 Sept 2026, 08:47 UTC · CWE-476 · NULL Pointer Dereference

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-24788
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceNIST NVD
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    a361293f5fedea0016a10599f409631a15d47ee7 < 2d2b648960147d078b000b9a7494017082024366; a361293f5fedea0016a10599f409631a15d47ee7 < e4325e84727e539c8597bd5b8491349f57f7fb17; a361293f5fedea0016a10599f409631a15d47ee7 < be54c0055407a73b60349c093c8ce621cb8fa232; a361293f5fedea0016a10599f409631a15d47ee7 < a070d5a872ffe0e0fe5c46eda6386140ded39adb; a361293f5fedea0016a10599f409631a15d47ee7 < e76bcb727e4874a2f9d0297f8e3f8eced89b0764; a361293f5fedea0016a10599f409631a15d47ee7 < 4855a59e21789c79f003a9b5f4135c95a7495c6b; a361293f5fedea0016a10599f409631a15d47ee7 < 33f486987af21531a7b18973d11795ede3da9ddd; a361293f5fedea0016a10599f409631a15d47ee7 < 1aec30021edd410b986c156f195f3d23959a9d11 · Fixed: < 3.11; 5.10.253 ≤ 5.10.*; 5.15.203 ≤ 5.15.*; 6.1.168 ≤ 6.1.*; 6.6.134 ≤ 6.6.*; 6.12.81 ≤ 6.12.*; 6.18.21 ≤ 6.18.*; 6.19.11 ≤ 6.19.*
    After
    Linux: a361293f5fedea0016a10599f409631a15d47ee7 < 2d2b648960147d078b000b9a7494017082024366, a361293f5fedea0016a10599f409631a15d47ee7 < e4325e84727e539c8597bd5b8491349f57f7fb17, a361293f5fedea0016a10599f409631a15d47ee7 < be54c0055407a73b60349c093c8ce621cb8fa232, a361293f5fedea0016a10599f409631a15d47ee7 < a070d5a872ffe0e0fe5c46eda6386140ded39adb, a361293f5fedea0016a10599f409631a15d47ee7 < e76bcb727e4874a2f9d0297f8e3f8eced89b0764, a361293f5fedea0016a10599f409631a15d47ee7 < 4855a59e21789c79f003a9b5f4135c95a7495c6b, a361293f5fedea0016a10599f409631a15d47ee7 < 33f486987af21531a7b18973d11795ede3da9ddd, a361293f5fedea0016a10599f409631a15d47ee7 < 1aec30021edd410b986c156f195f3d23959a9d11, 3.11 · Fixed: Linux: < 3.11, 5.10.253 ≤ 5.10.*, 5.15.203 ≤ 5.15.*, 6.1.168 ≤ 6.1.*, 6.6.134 ≤ 6.6.*, 6.12.81 ≤ 6.12.*, 6.18.21 ≤ 6.18.*, 6.19.11 ≤ 6.19.*, 7.0 ≤ *
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2026-24788↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Patch or update reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-31450 · cve.blacktree.nl