The AlmaLinux 9.6 host has packages installed that are affected by multiple vulnerabilities as referenced in the TuxCare ALMALINUX9.6:CLSA-2026:1778930898 advisory.

  - In the Linux kernel, the following vulnerability has been resolved: net: skbuff: propagate shared-frag     marker through frag-transfer helpers Two frag-transfer helpers (__pskb_copy_fclone() and skb_shift()) fail     to propagate the SKBFL_SHARED_FRAG bit in skb_shinfo()->flags when moving frags from source to     destination. __pskb_copy_fclone() defers the rest of the shinfo metadata to skb_copy_header() after     copying frag descriptors, but that helper only carries over gso_{size,segs, type} and never touches     skb_shinfo()->flags; skb_shift() moves frag descriptors directly and leaves flags untouched. As a result,     the destination skb keeps a reference to the same externally-owned or page-cache-backed pages while     reporting skb_has_shared_frag() as false. The mismatch is harmful in any in-place writer that uses     skb_has_shared_frag() to decide whether shared pages must be detoured through skb_cow_data(). ESP input is     one such writer (esp4.c, esp6.c), and a single nft 'dup to <local>' rule -- or any other nf_dup_ipv4() /     xt_TEE caller -- is enough to land a pskb_copy()'d skb in esp_input() with the marker stripped, letting an     unprivileged user write into the page cache of a root-owned read-only file via authencesn-ESN stray     writes. Set SKBFL_SHARED_FRAG on the destination whenever frag descriptors were actually moved from the     source. skb_copy() and skb_copy_expand() share skb_copy_header() too but linearize all paged data into     freshly allocated head storage and emerge with nr_frags == 0, so skb_has_shared_frag() returns false on     its own; they need no change. The same omission exists in skb_gro_receive() and skb_gro_receive_list().
    The former moves the incoming skb's frag descriptors into the accumulator's last sub-skb via two paths (a     direct frag-move loop and the head_frag + memcpy path); the latter chains the incoming skb whole onto p's     frag_list. Downstream skb_segment() reads only skb_shinfo(p)->flags, and skb_segment_list() reuses each     sub-skb's shinfo as the nskb -- both p and lp must carry the marker. The same omission also exists in     tcp_clone_payload(), which builds an MTU probe skb by moving frag descriptors from skbs on sk_write_queue     into a freshly allocated nskb. The helper falls into the same family and warrants the same fix for     consistency; no TCP TX-side in-place writer is currently known to reach a user page through this gap, but     a future consumer depending on the marker would regress silently. The same omission exists in     skb_segment(): the per-iteration flag merge takes only head_skb's flag, and the inner switch that rebinds     frag_skb to list_skb on head_skb-frags exhaustion does not fold the new frag_skb's flag into nskb. Fold     frag_skb's flag at both sites so segments drawing frags from frag_list members carry the marker.
    (CVE-2026-43503)

  - In the Linux kernel, the following vulnerability has been resolved: ptrace: slightly saner     'get_dumpable()' logic The 'dumpability' of a task is fundamentally about the memory image of the task -     the concept comes from whether it can core dump or not - and makes no sense when you don't have an     associated mm. And almost all users do in fact use it only for the case where the task has a mm pointer.
    But we have one odd special case: ptrace_may_access() uses 'dumpable' to check various other things     entirely independently of the MM (typically explicitly using flags like PTRACE_MODE_READ_FSCREDS).
    Including for threads that no longer have a VM (and maybe never did, like most kernel threads). It's not     what this flag was designed for, but it is what it is. The ptrace code does check that the uid/gid     matches, so you do have to be uid-0 to see kernel thread details, but this means that the traditional     drop capabilities model doesn't make any difference for this all. Make it all make a *bit* more sense by     saying that if you don't have a MM pointer, we'll use a cached last dumpability flag if the thread ever     had a MM (it will be zero for kernel threads since it is never set), and require a proper CAP_SYS_PTRACE     capability to override. (CVE-2026-46333)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Detections

Analytics

AlmaLinux 9.6 [TuxCare] Security Update: kernel / kernel-64k / kernel-64k-core / kernel-64k-debug / etc Multiple Vulnerabilities (ALMALINUX9.6:CLSA-2026:1778930898)

high Nessus Plugin ID 351723

Version 1.5

Version 1.4

Version 1.3

Version 1.1

Version 1.5 Oct 22, 2026, 10:08 AM CVSSv2 score source (changed from "CVE-2026-46333" to "CVE-2026-43503") CVSSv3 score source (set to "CVE-2026-46333") Exploit attributes ("Exploit framework core" set to "True") Exploit attributes ("Exploit framework metasploit" set to "True") Exploit attributes ("Exploited by malware" set to "True") Plugin Feed: 202610221008
Version 1.4 Oct 22, 2026, 12:02 AM CVE (set "CVE" coverage to "CVE-2026-43503,CVE-2026-46333") CVSS metrics ("CVSSv2 score" set to 6.8) CVSS metrics ("CVSSv2 vector" set to "CVSS2#AV:L/AC:L/Au:S/C:C/I:C/A:C") Detection (updated detection logic) Exploit attributes ("Exploited by malware" changed from "True" to none) Plugin metadata Plugin Feed: 202610220002
Version 1.3 Oct 15, 2026, 8:27 AM CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:H/RL:OF/RC:C") CVSS temporal metrics ("CVSSv3 temporal vector" set to "CVSS:3.0/E:H/RL:O/RC:C") Exploit attributes ("Exploited by malware" set to "True") Plugin Feed: 202610150827
Version 1.1 Sep 30, 2026, 9:32 PM New Plugin Feed: 202609302132