Skip to main content
VulnerabilityPublished Updated

CVE-2026-53199: Linux kernel · hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in fe7221b4346418d27ec2daccfc09df6692b76f0b : patch Linux kernel soon.

Data as of 26 Oct 2026, 17:30 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers can reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-10-16.

Patch
Available – fixed in fe7221b4346418d27ec2daccfc09df6692b76f0b, a82d4251918f37d9c5aab7b365157669fb885ec3, 16514afeb7d3d121072ba9a0b640d6c1c5507db0 +5
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ c25aaf814a63f9d9c4e45416f13d70ef0aa0be2e, < fe7221b4346418d27ec2daccfc09df6692b76f0b
Fixed in
  • fe7221b4346418d27ec2daccfc09df6692b76f0b
LinuxLinuxAffected
  • ≥ c25aaf814a63f9d9c4e45416f13d70ef0aa0be2e, < a82d4251918f37d9c5aab7b365157669fb885ec3
Fixed in
  • a82d4251918f37d9c5aab7b365157669fb885ec3
LinuxLinuxAffected
  • ≥ c25aaf814a63f9d9c4e45416f13d70ef0aa0be2e, < 16514afeb7d3d121072ba9a0b640d6c1c5507db0
Fixed in
  • 16514afeb7d3d121072ba9a0b640d6c1c5507db0
LinuxLinuxAffected
  • ≥ c25aaf814a63f9d9c4e45416f13d70ef0aa0be2e, < 918c0c988239aa5ab96b254e504d191af6191061
Fixed in
  • 918c0c988239aa5ab96b254e504d191af6191061
LinuxLinuxAffected
  • ≥ c25aaf814a63f9d9c4e45416f13d70ef0aa0be2e, < 695c59cf7bf707e6ff8cea01916ee50e86616933
Fixed in
  • 695c59cf7bf707e6ff8cea01916ee50e86616933
LinuxLinuxAffected
  • ≥ c25aaf814a63f9d9c4e45416f13d70ef0aa0be2e, < 09b8a7aa5a341bb345dc492aac139525efa13515
Fixed in
  • 09b8a7aa5a341bb345dc492aac139525efa13515

Description

In the Linux kernel, the following vulnerability has been resolved: hv_netvsc: use kmap_local_page in netvsc_copy_to_send_buf netvsc_copy_to_send_buf() copies page buffer entries into the VMBus send buffer using phys_to_virt() on the entry PFN. Entries for the RNDIS header and the skb linear data come from kmalloc'd memory and are always in the kernel direct map, but entries for skb fragments reference page cache or user pages, which on 32-bit x86 with CONFIG_HIGHMEM=y can live above the LOWMEM boundary. For such a page phys_to_virt() returns an address outside the direct map and the subsequent memcpy() faults on the transmit softirq path, which is fatal. Map the pages with kmap_local_page() instead, handling two properties of the page buffer entries: - pb[i].pfn is a Hyper-V PFN at HV_HYP_PAGE_SIZE (4K) granularity, not a native PFN. Reconstruct the physical address first and derive the native page from it, so the mapping stays correct where PAGE_SIZE > HV_HYP_PAGE_SIZE (e.g. arm64 with 64K pages). - Since commit 41a6328b2c55 ("hv_netvsc: Preserve contiguous PFN grouping in the page buffer array"), an entry describes a full physically contiguous fragment and pb[i].len can exceed PAGE_SIZE, while kmap_local_page() maps a single page. Copy page by page, splitting at native page boundaries. The copy path only handles packets smaller than the send section size (6144 bytes by default); larger packets take the cp_partial path where only the RNDIS header is copied. So entries here are bounded by the section size and a copy is split at most once on 4K-page systems. On !CONFIG_HIGHMEM configs kmap_local_page() folds to page_address() and no mapping work is added.

References

Community reviews

Loading reviews…