An update of the linux package has been released.

The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available.

  - tcp: fix AO info use-after-free in tcp_ao_connect_init() tcp_v4_connect() adds a SYN-SENT socket to the     ehash before calling tcp_connect(). If TCP-AO is configured, tcp_connect() first verifies that a key     matches the peer and the bound device's current L3 master. tcp_ao_connect_init() later resolves the L3     master again and removes keys which do not match it. The socket lock does not stabilize the bound device's     VRF membership. Detaching the device from its VRF between the initial validation and the L3-master     calculation in tcp_ao_connect_init() can therefore make the validation succeed while initialization     observes the default L3 domain and removes the only key. The subsequent AO lookup then fails, so the no-     key path clears tp->ao_info and frees it directly. The receive path can find the socket in the ehash and     load tp->ao_info under RCU before acquiring the socket lock. A reader which loaded the old pointer can     thus continue into tcp_inbound_ao_hash() after the direct free. The issue was found during a static audit     of TCP-AO object lifetime. An unprivileged reproducer in self-created user and network namespaces raced     connect() with detaching a veth from its VRF while sending TCP-AO segments. It triggered the same KASAN     report on two fresh boots: BUG: KASAN: slab-use-after-free in tcp_inbound_ao_hash+0x585/0x19f0 Write of     size 8 at addr ffff88800bf88128 by task tcp_ao_vrf_race/232 Call Trace: tcp_inbound_ao_hash+0x585/0x19f0     tcp_inbound_hash+0x677/0xa80 tcp_v4_rcv+0x1c3e/0x3ab0 Allocated by task 235: tcp_ao_alloc_info+0x43/0xf0     tcp_ao_add_cmd+0xdf7/0x13b0 do_tcp_setsockopt+0x168c/0x2640 Freed by task 235: kfree+0x1b8/0x550     tcp_connect+0x252/0x4f00 tcp_v4_connect+0x1114/0x1720 The bad address is 40 bytes inside the freed     128-byte object, matching the tcp_ao_info counters.key_not_found field. The two runs used 1000 attempts     each, reached the no-key path 366 and 411 times, and produced one and two KASAN reports respectively. With     this change, the same reproducer reached the no-key path 366 times in 1000 attempts without a KASAN report     or oops. Use tcp_ao_destroy_sock() for the no-key path. It unpublishes the AO info, updates the socket     memory and static-key accounting, and defers the free until after an RCU grace period. Also drop the     WARN_ON_ONCE() and its stale comment. The VRF detach race makes the no-key state reachable during normal     operation, so it is a handled condition rather than an impossible assertion. On panic_on_warn kernels the     WARN would turn this handled race into a kernel panic. (CVE-2026-80850)

Note that Nessus relies on the presence of the package as reported by the vendor.

ID	Name	Product	Family	Published	Updated	Severity
375011	Photon OS 5.0: Linux PHSA-2026-5.0-91-0999	Nessus	PhotonOS Local Security Checks	11/2/2026	11/2/2026	high
351155	Debian dsa-6528 : ata-modules-6.12.111+deb13-armmp-di - security update	Nessus	Debian Local Security Checks	9/29/2026	9/29/2026	high
362907	Debian dla-4817 : ata-modules-6.12.107+deb12-armmp-di - security update	Nessus	Debian Local Security Checks	10/4/2026	10/4/2026	high
342949	Linux Distros Unpatched Vulnerability : CVE-2026-80850	Nessus	Misc.	9/4/2026	11/6/2026	high
375048	Photon OS 5.0: Linux PHSA-2026-5.0-92-0999	Nessus	PhotonOS Local Security Checks	11/2/2026	11/2/2026	high
376443	Ubuntu 24.04 LTS / 26.04 LTS : Linux kernel vulnerabilities (USN-8959-1)	Nessus	Ubuntu Local Security Checks	11/5/2026	11/5/2026	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high