# CVE-2026-68292: linux: In the Linux kernel, the following vulnerability has been resolved:  ice: prevent tstamp ring allocation for non-PF V...

CVE-2026-68292 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-68292, released August 11, 2026. It is not reported as exploited. Patch Radar priority: High.

- Web page: https://patchblox.com/security/cve/CVE-2026-68292
- Priority: High
- CVSS: n/a (important)
- EPSS: 0.0017
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Aug 10, 2026

## Description

In the Linux kernel, the following vulnerability has been resolved:  ice: prevent tstamp ring allocation for non-PF VSI types  The pf->txtime_txqs bitmap tracks which Tx queues have ETF (Earliest TxTime First) offload enabled. This bitmap is indexed by queue number and is set by ice_offload_txtime(), which only operates on PF VSI queues.  However, ice_is_txtime_ena() does not check the VSI type before consulting the bitmap. When ETF offload is enabled on PF Tx queue 0, bit 0 is set in pf->txtime_txqs. During a subsequent PCI reset rebuild, the CTRL VSI's Tx queue 0 is reconfigured and ice_is_txtime_ena() is called for that ring. Since it only checks pf->txtime_txqs by queue index without distinguishing VSI type, it finds bit 0 set and returns true, matching the PF VSI's ETF queue, not the CTRL VSI's. This causes ice_vsi_cfg_txq() to spuriously allocate a tstamp_ring for the CTRL VSI ring.  Since CTRL VSI rings have no associated netdev, ice_clean_tx_ring() takes an early return at the !netdev check before reaching ice_free_tx_tstamp_ring(), leaking the allocation. Each PCI reset leaks one 64-byte tstamp_ring.  Fix this by restricting ice_is_txtime_ena() to return true only for PF VSI rings, since txtime_txqs is only meaningful for PF VSI queues.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | bpftool6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | bpftool6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel-livepatch-6.18.44-99.149 amzn 2023 | 1:1.0-0.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-debuginfo-common-aarch64 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-debuginfo-common-x86_64 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-devel amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-headers amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-modules-extra amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-modules-extra-common amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-tools amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-tools-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | kernel6.18-tools-devel amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | linux Debian 14 | 7.1.6-1 | [DEBIAN-CVE-2026-68292](https://patchblox.com/security/data/fix/linux/debian-cve-2026-68292.md) | Aug 11, 2026 |
| Linux | microvm-kernel6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | perf6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | perf6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | python3-perf6.18 amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |
| Linux | python3-perf6.18-debuginfo amzn 2023 | 1:6.18.44-99.149.amzn2023 | [ALAS2023-2026-2106](https://patchblox.com/security/data/fix/linux/alas2023-2026-2106.md) | Aug 31, 2026 |

---

Data as of 2026-11-09T01:18:40Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.
