Vulnpedia
← Search CVEs

CVE-2026-93262

HIGH 7.8

Published 2026-09-24 · Last modified 2026-10-19

In the Linux kernel, the following vulnerability has been resolved: md/raid5-ppl: fix use-after-free in ppl_do_flush() The loop in ppl_do_flush() continues iterating after calling ppl_io_unit_finished(), touching io->pending_flushes and leading to a use-after-free. Add a break statement to stop the loop once io is freed.

ELEVATED IMPACT

Severe if exploited (CVSS 7.8), but no known exploitation and low modeled probability. Patch on a normal cadence.

Exploitation likelihood

0.2%chance of exploitation in 30 days · 4th percentile

○ In CISA KEV ○ Catalogued PoC

Impact if exploited

7.8CVSS 3.1 · HIGH

  • ConfidentialityHigh
  • IntegrityHigh
  • AvailabilityHigh

What an attacker needs

  • ⚠Access: Requires local access to the host
  • ⚠Privileges: Requires a low-privilege account
  • ✓User interaction: No user interaction needed
  • ✓Complexity: No special conditions — reliably repeatable

✓ lowers the bar for an attacker · ⚠ raises it

Proof of concept

No public PoC is currently catalogued.

Search for new PoCs

Search GitHub now — results may be empty or unverified.

Tracked sources are checked daily for recent CVEs, including PoCs published after the original disclosure. A later release appears after a tracked source lists it and a refresh succeeds.

Data snapshot:

Affected

Vendors Linux

Products Linux

Weakness (CWE)

Not classified.

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References and research data (JSON)

Vendor product assessments

Showing 32 of 377 vendor product statements; 345 omitted. Read the full vendor advisory.

  • bpftool-0:4.18.0-553.174.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=aarch64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-core-0:4.18.0-553.174.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=ppc64le

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-debug-devel-0:4.18.0-553.174.1.el8_10.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=aarch64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-debuginfo-0:4.18.0-553.174.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=x86_64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-modules-extra-0:4.18.0-553.174.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=ppc64le

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-zfcpdump-0:4.18.0-553.174.1.el8_10.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=s390x

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • python3-perf-0:4.18.0-553.174.1.el8_10.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=ppc64le

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-debuginfo-0:4.18.0-553.174.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux CRB (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=x86_64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • python3-perf-debuginfo-0:4.18.0-553.174.1.el8_10.x86_64 as a component of Red Hat Enterprise Linux CRB (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=x86_64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-modules-0:4.18.0-553.174.1.rt7.515.el8_10.x86_64 as a component of Red Hat Enterprise Linux NFV (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=x86_64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-modules-extra-0:4.18.0-553.174.1.rt7.515.el8_10.x86_64 as a component of Red Hat Enterprise Linux RT (v. 8) · fixed

    Vendor assessment for this product only.

    pkg:rpm/redhat/[email protected]_10?arch=x86_64

    • vendor fix: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 The system must be rebooted for this update to take effect. Red Hat recommends treating all kernel errata as security-relevant. Given the kernel's fundamental role, any bug has a higher chance of impacting system security, even if that impact only becomes clear after a fix is published. Therefore, Red Hat prioritizes delivering fixes that improve our customers' overall security posture. Because of this proactive approach, a patch may be associated with a CVE assignment at a future date. Retroactive CVE assignments are always documented in the corresponding errata and on Red Hat's CVE pages. We strongly advise against delaying updates, as doing so may leave your system exposed when protections are already available. Vendor guidance
    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel as a component of Red Hat Enterprise Linux 10 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-debug-core as a component of Red Hat Enterprise Linux 10 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-debug-core

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-64k-debug-core as a component of Red Hat Enterprise Linux 10 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-rt-64k-debug-core

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-kvm as a component of Red Hat Enterprise Linux 10 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-rt-kvm

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • python3-perf as a component of Red Hat Enterprise Linux 10 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/python3-perf

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-64k-modules as a component of Red Hat Enterprise Linux 9 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-64k-modules

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-debug-uki-virt-addons as a component of Red Hat Enterprise Linux 9 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-debug-uki-virt-addons

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-64k-debug-modules as a component of Red Hat Enterprise Linux 9 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-rt-64k-debug-modules

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-debug-kvm as a component of Red Hat Enterprise Linux 9 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-rt-debug-kvm

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-tools-libs-devel as a component of Red Hat Enterprise Linux 9 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/kernel-tools-libs-devel

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • rv as a component of Red Hat Enterprise Linux 9 · known affected

    Vendor assessment for this product only.

    pkg:rpm/redhat/rv

    • workaround: Prevent the `raid456` kernel module from loading if software RAID 4, 5, or 6 functionality is not required. 1. Add the blacklist configuration by creating `/etc/modprobe.d/blacklist-raid456.conf` with the following entries: blacklist raid456 install raid456 /bin/true 2. Unload the module if it is currently loaded: # modprobe -r raid456 Warning: If software RAID 4, 5, or 6 is currently in use or required for storage arrays, this workaround cannot be applied, as disabling the module will prevent storage devices from functioning. A system reboot may be required if the module is actively in use by existing mounts.
    • none available: Affected
    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel as a component of Red Hat Enterprise Linux 6 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-devel as a component of Red Hat Enterprise Linux 6 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-devel

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-kdump as a component of Red Hat Enterprise Linux 6 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-kdump

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • bpftool as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/bpftool

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-debug as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-debug

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-kdump as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-kdump

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-debug-devel as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-rt-debug-devel

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-rt-trace as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-rt-trace

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • kernel-tools as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/kernel-tools

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00
  • python-perf as a component of Red Hat Enterprise Linux 7 · known not affected

    Vendor assessment for this product only.

    Reason: vulnerable code not present

    pkg:rpm/redhat/python-perf

    Red Hat · CVE-2026-93262 · Updated 2026-10-14T22:59:38+00:00

All CVSS metrics

  • HIGH 7.8 v3.1 · CNA Primary
    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
  • HIGH 7.8 v3.1 · NVD Secondary
    CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

Advisories

Technical & other

Sources: NVD · CVE.org · EPSS