CVE-2026-97997

Что произошло

In the Linux kernel, the following vulnerability has been resolved: virtio_ring: fix stale descriptor flags after a failed packed add In a packed ring the AVAIL and USED bits sit in the descriptor itself, so writing them makes that descriptor available. Those bit combinations flip meaning on every round of the ring, tracked by a wrap counter, so invalidating or validating a descriptor means inverting both bits. Commit 1ce9e6055fa0 ("virtio_ring: introduce packed ring support") has virtqueue_add_packed() make every descriptor of a chain available as it maps the chain, and write the head last. The device consumes the ring in order and stops at a head that is not available yet, so it never reaches the rest. When vring_map_one_sg() fails partway, unmap_release unmaps the segments and restores avail_used_flags, but the descriptors it wrote to in the ring stay marked with AVAIL and USED bits. The head is now the only entry that keeps the device from consuming these stale entries. For example, the ring would look like this now. Z - pre-previous command A - previous command B - aborted command C - current command [A1 DONE] [A2 DONE] [B2] [B3] [Z1 DONE] When the driver now attempts to issue the C command, the next add starts at the same head as B. If C spans less descriptors than B, there is no end marker because AVAIL and USED bits were still in place. And that means the device will start interpreting these stale entries (B2/B3) as another command entry, which then blocks the queue. This effect typically happens in swiotlb configurations under memory pressure, because vring_map_one_sg() can then fail with larger I/O requests which then leads to command abortions. There are broadly 2 ways to avoid leaving those flags behind: 1) Defer those flags too until the chain is complete. 2) Rewrite those flags for the previous wrap counter. Implement the second option in both packed add paths. The first option traverses the chain a second time on every successful add. The second option invalidates all added descriptors when any add fails. With this patch applied, a packed virtqueue keeps completing requests after a failed add.

Что делать

dpkg-query -W -f='${Package}	${Version}\n'

rpm -qa --qf '%{NAME}\t%{VERSION}-%{RELEASE}\n'

Get-HotFix | Select-Object HotFixID, InstalledOn

Продукты и затронутые версии

{
  "status": "affected",
  "version": "1ce9e6055fa0a9043405c5604cf19169ec5379ff",
  "lessThan": "5ad081761a1f0b0d95ab08b61a6008309fba95f9",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "1ce9e6055fa0a9043405c5604cf19169ec5379ff",
  "lessThan": "cfe8128ceb78374b0f9cebb608bb48e3928d784a",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "1ce9e6055fa0a9043405c5604cf19169ec5379ff",
  "lessThan": "3e6400e3b8b858cdf0f8d70b20d8b55d703af368",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "1ce9e6055fa0a9043405c5604cf19169ec5379ff",
  "lessThan": "d595358276b60e5df4d3930bc94033249b1d5adc",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "1ce9e6055fa0a9043405c5604cf19169ec5379ff",
  "lessThan": "75d276e5bb68778b2916f98a2bc30f142ebadc64",
  "versionType": "git"
}

{
  "status": "affected",
  "version": "5.0"
}

{
  "status": "unaffected",
  "version": "0",
  "lessThan": "5.0",
  "versionType": "semver"
}

{
  "status": "unaffected",
  "version": "6.6.160",
  "versionType": "semver",
  "lessThanOrEqual": "6.6.*"
}

{
  "status": "unaffected",
  "version": "6.12.114",
  "versionType": "semver",
  "lessThanOrEqual": "6.12.*"
}

{
  "status": "unaffected",
  "version": "6.18.57",
  "versionType": "semver",
  "lessThanOrEqual": "6.18.*"
}

{
  "status": "unaffected",
  "version": "7.2.7",
  "versionType": "semver",
  "lessThanOrEqual": "7.2.*"
}

{
  "status": "unaffected",
  "version": "7.3",
  "versionType": "original_commit_for_fix",
  "lessThanOrEqual": "*"
}

CVSS: оценки и векторы

Оценка CVSS отсутствует.

Источники и ссылки

{
  "cwes": [],
  "epss": {
    "source": "epss",
    "received_at": "2026-11-03T21:16:04.209862+00:00"
  },
  "title": {
    "source": "cve",
    "received_at": "2026-10-28T21:30:02.241899+00:00"
  },
  "scores": [],
  "status": {
    "source": "cve",
    "received_at": "2026-10-28T21:30:02.241899+00:00"
  },
  "affected": [
    "cve"
  ],
  "published": {
    "source": "cve",
    "received_at": "2026-10-28T21:30:02.241899+00:00"
  },
  "solutions": [],
  "percentile": {
    "source": "epss",
    "received_at": "2026-11-03T21:16:04.209862+00:00"
  },
  "references": [
    "cve"
  ],
  "description": {
    "source": "cve",
    "received_at": "2026-10-28T21:30:02.241899+00:00"
  },
  "workarounds": [],
  "configurations": []
}

Хронология записи

1. Данные обновлены04.11.2026, 00:16
2. Данные обновлены03.11.2026, 00:15
3. Данные обновлены02.11.2026, 00:13
4. Данные обновлены31.10.2026, 12:00
5. Данные обновлены29.10.2026, 12:47
6. Опубликована29.10.2026, 00:30

Личная заметка и статус

Другие CVE того же продукта