Improper Validation of Specified Quantity in Input Affecting kernel-rt-debug-modules-internal package, versions *
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RHEL8-KERNELRTDEBUGMODULESINTERNAL-20192168
- published28 Sept 2026
- disclosed24 Sept 2026
Introduced: 24 Sep 2026
NewCVE-2026-93271 (opens in a new tab)How to fix?
There is no fixed version for RHEL:8 kernel-rt-debug-modules-internal.
NVD Description
Note: Versions mentioned in the description apply only to the upstream kernel-rt-debug-modules-internal package and not the kernel-rt-debug-modules-internal package as distributed by RHEL.
See How to fix? for RHEL:8 relevant fixed versions and status.
In the Linux kernel, the following vulnerability has been resolved:
wifi: ath11k: cap out-of-range rx MCS instead of leaving bogus rate
ath11k can receive HT/VHT/HE frames whose reported MCS is above the maximum that can be expressed in the corresponding mac80211 rate space (e.g. an HE frame reported with MCS 12, while HE tops out at MCS 11).
The frame itself is valid and decodes correctly, but for such a frame ath11k_dp_rx_h_rate() leaves rx_status->rate_idx set to the out-of-range value and never assigns rx_status->encoding, so it stays RX_ENC_LEGACY from the ath11k_dp_rx_h_ppdu() initialization. Once that frame reaches mac80211 it trips the rate sanity check and the frame is dropped with a splat:
ath11k_pci 0000:03:00.0: Received with invalid mcs in HE mode 12 WARNING: CPU: 0 PID: 0 at net/mac80211/rx.c:5433 ieee80211_rx_list+0xb0a/0xe90 [mac80211]
Dropping the frame would discard otherwise valid data, so instead cap the reported MCS to the maximum the rate space can express and deliver the frame. Set rx_status->encoding before the range check and assign rate_idx from the capped value, so a frame with an out-of-range MCS no longer leaves partial or bogus rate metadata behind. Also downgrade the logging level since they are not treated as invalid frames now. The only loss is that such a frame is reported as the capped MCS in the rx rate statistics.
Tested-on: WCN6855 hw2.1 PCI WLAN.HSP.1.1-03125-QCAHSPSWPL_V1_V2_SILICONZ_LITE-3.6510.41
References
- https://access.redhat.com/security/cve/CVE-2026-93271
- https://git.kernel.org/stable/c/12b09e478aa7459b7893a695ef77682202f2da83
- https://git.kernel.org/stable/c/2bb2a778a487305bd378db5fd5014fbdce4ada2c
- https://git.kernel.org/stable/c/6ad04c3e2ec54bf5ec72c81afdd66318a116c539
- https://git.kernel.org/stable/c/a0b3e6f9645d88f387c4fea546048a91952cd4cd
- https://git.kernel.org/stable/c/a6b951f79e66fc8bd93a537ff1040fbfb567c8bf
- https://git.kernel.org/stable/c/b77bfe6e59b98dff3ccfcf9b45fc27e3db498626
- https://git.kernel.org/stable/c/ccbd20f2168f581d90265da1a925b9b6472a0b05
- https://git.kernel.org/stable/c/fb7b9a7209f839c17c66484dfdc84c9a23c6fd2f