{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-23057 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-23057 is a vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-23057 and fix it if it is affected.\n\nWhat it is: CVE-2026-23057 is a vulnerability in Linux, published on 4 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-23057 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-23057/ (Markdown: https://insights.sbomify.com/CVE-2026-23057/index.md)","id":"CVE-2026-23057","markdown":"https://insights.sbomify.com/CVE-2026-23057/index.md","name":"CVE-2026-23057","record":{"aliases":["BELL-CVE-2026-23057","DEBIAN-CVE-2026-23057","GHSA-2725-mxxg-w826","ROOT-OS-DEBIAN-13-CVE-2026-23057","ROOT-OS-UBUNTU-2404-CVE-2026-23057","UBUNTU-CVE-2026-23057"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel vsock","requires_auth":"none","summary":"A flaw in Linux kernel vsock/virtio allows uninitialized kernel memory disclosure when coalescing non-linear skbs in loopback transport.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nvsock/virtio: Coalesce only linear skb\n\nvsock/virtio common tries to coalesce buffers in rx queue: if a linear skb\n(with a spare tail room) is followed by a small skb (length limited by\nGOOD_COPY_LEN = 128), an attempt is made to join them.\n\nSince the introduction of MSG_ZEROCOPY support, assumption that a small skb\nwill always be linear is incorrect. In the zerocopy case, data is lost and\nthe linear skb is appended with uninitialized kernel memory.\n\nOf all 3 supported virtio-based transports, only loopback-transport is\naffected. G2H virtio-transport rx queue operates on explicitly linear skbs;\nsee virtio_vsock_alloc_linear_skb() in virtio_vsock_rx_fill(). H2G\nvhost-transport may allocate non-linear skbs, but only for sizes that are\nnot considered for coalescence; see PAGE_ALLOC_COSTLY_ORDER in\nvirtio_vsock_alloc_skb().\n\nEnsure only linear skbs are coalesced. Note that skb_tailroom(last_skb) \u003e 0\nguarantees last_skb is linear.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"vsock/virtio: Coalesce only linear skb","id":"CVE-2026-23057","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"can: ems_usb: ems_usb_read_bulk_callback(): fix URB memory leak","id":"CVE-2026-23058"},"packages":[],"prev":{"headline":"uacce: implement mremap in uacce_vm_ops to return -EPERM","id":"CVE-2026-23056"},"products":["Linux"],"published":"2026-02-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A flaw in Linux kernel vsock/virtio allows uninitialized kernel memory disclosure when coalescing non-linear skbs in loopback transport.","url":"https://insights.sbomify.com/CVE-2026-23057/"}