Skip to main content
VulnerabilityPublished

CVE-2026-99723: Linux kernel · vhost-vdpa: fix pinned page leak in vhost_vdpa_pa_map() error path

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-99723· Medium

Not known to be exploited · fixed in fd1462c96bafe2cb14e88c837b270f8990b717b5 : update Linux kernel when convenient.

Data as of 20 Nov 2026, 07:34 UTC

Severity
Medium

Rated by Threat Radar · CVSS not yet scored by NVD

Thin evidence

One scorer or none
Patch
Available – fixed in fd1462c96bafe2cb14e88c837b270f8990b717b5, 441039451a19e171a1d6376b8b16e1b90316d119, 77bd4305f34f65630e26a108ec98555d6aafce37 +2

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=5.9.15 <5.10
Fixed in
  • fd1462c96bafe2cb14e88c837b270f8990b717b5
  • 441039451a19e171a1d6376b8b16e1b90316d119
  • 77bd4305f34f65630e26a108ec98555d6aafce37
  • 5b9af57dba47a1750be4831da1f1f34c99c50caa
  • 5.10
LinuxLinuxAffected
  • =5.10
Fixed in–

Description

In the Linux kernel, the following vulnerability has been resolved: vhost-vdpa: fix pinned page leak in vhost_vdpa_pa_map() error path When pin_user_pages() or vhost_vdpa_map() fails, vhost_vdpa_pa_map() is supposed to unpin the pages pinned after the last successfully mapped chunk, i.e. the range [map_pfn, last_pfn]. The unpin is guarded by nchunks, but nchunks is reset to 0 every time a chunk is mapped from inside the current page list, so a failure after any such boundary leaves that pending range pinned forever. With physically scattered memory nearly every page list contains a boundary, so the leak happens on practically every failed IOTLB update. The pending range is non-empty exactly when a page has been pinned, which last_pfn already tells us, so drop nchunks and test last_pfn.

References

Community reviews

Loading reviews…