CVE-2026-43494 / CVE-2026-43502 — PinTheft tracking

This tracker is no longer updated. Every tracked distribution has shipped a PinTheft fix or was never affected, and both fix commits are present in all supported mainline, LTS, and 7.x stable kernels.

Summary

An unprivileged local user can obtain root on a kernel that exposes the RDS (Reliable Datagram Sockets) subsystem. The bug is a reference-count double-free in the RDS zero-copy send path:

• rds_message_zcopy_from_user() pins user pages one at a time. If a later page faults, the error path releases the pages it has already pinned — but leaves the scatterlist entries and the op_nents count live after clearing op_mmp_znotifier. When rds_message_purge() later runs from rds_sendmsg(), its cleanup loop iterates the stale op_nents and frees the same pages a second time.
• Each failing zero-copy sendmsg() therefore steals exactly one reference from the first page of the send buffer.

On its own this is a refcount underflow. The PoC weaponises it with io_uring: it registers an anonymous page as an io_uring fixed buffer (IORING_REGISTER_BUFFERS), which adds a FOLL_PIN bias of GUP_PIN_COUNTING_BIAS (1024) to the page. 1024 failing RDS zero-copy sends then drain that bias while io_uring still holds the raw struct page *. The page is freed cleanly, reclaimed as page cache for a readable SUID-root binary, and the stale fixed-buffer entry is used via IORING_OP_READ_FIXED to overwrite that page cache with a small ELF payload. Executing the SUID binary then drops into a root shell.

Because the corruption lands in the host-wide page cache, the on-disk file is never modified — checksums, inotify, auditd file watches, and tripwire-style integrity tools do not detect exploitation. The overwrite is transient: dropping the page cache or rebooting clears it.

ℹ️ PinTheft is only exploitable where the RDS subsystem is actually reachable. Kernels built with # CONFIG_RDS is not set are not affected at all; kernels that ship RDS as a module (CONFIG_RDS=m) are affected only while the attacker can get rds/rds_tcp loaded — see Mitigation and the per-distro notes below.

Vulnerable commit range

Both fixes name the same introducing commit in their Fixes: tag (0cebaccef3ac "rds: zerocopy Tx support."). The effective lifetime of the bug is therefore about 8 years (2018–2026): every supported stable branch contains the vulnerable code.

The complete fix is both commits. 44b550d88b26 restructures the early-failure cleanup and is the one carrying Cc: stable, so it is the commit expected to flow into the stable trees; e17492979319 is a smaller follow-up correctness fix. A distro backport should include both — verifying only the presence of 44b550d88b26 is insufficient.

Upstream fixed versions

RDS zero-copy Tx support landed in v4.17, so every branch above carries the vulnerable code. Both fixes landed in mainline 7.1 (released 2026-06-14); 7.2-rc2 is current mainline. The fixes have backported to all actively maintained older stable branches: 6.18.y, 6.12.y, 6.6.y, 6.1.y, 5.15.y, and 5.10.y (see Notes column), making all those branches fully fixed as of their latest point releases. The 7.1.y tracking branch carries both fixes from the initial release. The 7.0.y branch (non-LTS, EOL 2026-06-27 at v7.0.14) also carries both fixes, backported before EOL. The short-lived non-LTS stable branches between the LTS lines (6.13.y through 6.17.y, and 6.19.y) all reached EOL before PinTheft was disclosed and never received the fix backports; they are omitted here except 6.17.y, which is retained as the upstream base for Proxmox PVE 9’s 6.17.x kernel (Proxmox backports the fix into its own kernel tree — see the Proxmox section).

Distribution status

A distribution is exploitable only if RDS is built (=y or =m) and the attacker can reach it. Where RDS ships as a module, the PoC relies on the SO_RDS_TRANSPORT=2 (RDS_TRANS_TCP) socket option autoloading rds_tcp; distributions that block unprivileged module autoloading raise the bar accordingly.

A distro that blocks that autoload by default — via a kernel patch or a modprobe.d drop-in — is marked mitigated, not fixed (⚠️): the double-free is still built and stays exploitable once rds is loaded by other means (an administrator modprobe, or a workload that uses RDS). A mitigation reduces exposure; it is not a fix, and it does not earn a ✅.

Debian

Debian ships the RDS subsystem as a module (CONFIG_RDS=m, CONFIG_RDS_TCP=m) across all current suites.

CONFIG_RDS=m on Debian 11 and 13 was confirmed by direct kernel-config inspection; Debian 12 carries the same long-standing module setting.

Debian carries a long-standing kernel patch (rds-Disable-auto-loading-as-mitigation-against-local.patch, Ben Hutchings, 2010) that comments out MODULE_ALIAS_NETPROTO(PF_RDS) in net/rds/af_rds.c. With no net-pf-21 module alias, an unprivileged socket(AF_RDS, …) cannot autoload rds, so the PoC’s SO_RDS_TRANSPORT=2 autoload trigger is closed by default — and more firmly than a modprobe.d drop-in, since it is compiled into the kernel binary. The patch is present in the kernel series of every tracked suite (debian/latest for sid/forky, and the trixie, bookworm, and bullseye security branches).

DSA-6305-1 (2026-05-28) brought a kernel patch to trixie with linux 6.12.90-2 (trixie-security pocket); the advisory explicitly covers CVE-2026-43494 (fix part 2, e17492979319); fix part 1 (44b550d88b26) was already present in the upstream 6.12.90 base (first in v6.12.88), so 6.12.90-2 is fully protected against both PinTheft CVEs. DSA-6355-1 (2026-06-27) updated trixie to linux 6.12.94-1 (trixie-security); the Debian security tracker records CVE-2026-43502 (fix part 1) as fixed at this version. DLA-4665-1 (2026-07-03) fixed bookworm with linux 6.1.176-1 (bookworm-security pocket); upstream 6.1.175 carries both fix commits (1e262db7675e and d84ce1786ce4), so 6.1.176-1 is fully protected against both PinTheft CVEs. DLA-4664-1 (2026-07-03) fixed bullseye with linux 5.10.259-1 (bullseye-security pocket); upstream 5.10.258 carries both fix commits (e9aefdc5c53f and c6e51512a784), so 5.10.259-1 is fully protected.

Proxmox Virtual Environment

Proxmox ships its own proxmox-kernel packages built on an Ubuntu-derived kernel tree.

Proxmox acknowledged PinTheft in PSA-2026-00022-1 (2026-05-19); PSA-2026-00022-2 (2026-05-29) followed with patched kernel packages for PVE 8 and PVE 9.

CONFIG_RDS=m on PVE 9 was confirmed by kernel-config inspection, and PVE 9 ships no autoload block — verified on a running host:

• modinfo on the proxmox-kernel rds.ko shows alias: net-pf-21 intact, so the kernel does not carry Debian’s autoload-disable patch.
• modprobe -c resolves net-pf-21 straight to the rds module with no stock modprobe.d drop-in disabling it.

Proxmox takes its kernel from Ubuntu but its userland from Debian, so it inherits neither parent’s mitigation: Debian’s lives in the kernel source (and Proxmox builds its own kernel), while Ubuntu’s net-pf-21 blacklist lives in the kmod package (and Proxmox ships Debian’s kmod). A stock PVE 9 host therefore autoloads rds on demand for an unprivileged user, exactly like Arch. PVE 8 is the same: the rds.ko in the proxmox-kernel-6.8.12-9-pve package likewise carries alias: net-pf-21, and PVE 8 shares the Debian-userland / Ubuntu-derived-kernel structure that leaves it without a modprobe.d block.

NixOS

NixOS builds RDS as a module (CONFIG_RDS=m), but an unprivileged process cannot autoload it: NixOS enables the Ubuntu module blacklist by default — boot.modprobeConfig.useUbuntuModuleBlacklist defaults to true on both nixos-unstable and nixos-25.11 — which installs /etc/modprobe.d/ubuntu.conf. That file carries Ubuntu’s blacklist-rare-network.conf, which includes:

# rds
alias net-pf-21 off

A socket(AF_RDS, …) from an unprivileged process makes the kernel issue request_module("net-pf-21"); the alias resolves net-pf-21 to the non-existent module off, so rds does not autoload. The PoC’s autoload-driven entry is blocked by default.

Both kernel bumps landed in nixpkgs on 2026-05-23; the nixos-unstable channel picked them up the same day, while nixos-25.11 advanced on 2026-05-26. The Ubuntu module blacklist (boot.modprobeConfig.useUbuntuModuleBlacklist, default true) continues to ship on both channels as an additional layer of defence-in-depth. The other modprobe.d files NixOS ships do not affect RDS: debian.conf (Debian module aliases), systemd.conf (bonding / dummy / ifb options), and firmware.conf (firmware search path). nixos.conf is empty unless boot.blacklistedKernelModules or boot.extraModprobeConfig is set.

Rocky Linux

The RHEL family does not build the RDS subsystem — the kernel config ships # CONFIG_RDS is not set, so the vulnerable code is absent entirely and no mitigation is required. All three releases were confirmed against the Rocky kernel configs in git.rockylinux.org: branch r8 (SOURCES/kernel-x86_64.config) and branches r9 and r10 (SOURCES/kernel-x86_64-rhel.config). The same is expected to hold for RHEL, AlmaLinux, and other RHEL rebuilds, but verify per build if in doubt.

Amazon Linux

Amazon builds the RDS subsystem as a loadable module — CONFIG_RDS=m, CONFIG_RDS_TCP=m — on every Amazon Linux kernel inspected, with CONFIG_IO_URING=y.

Amazon Linux 2023

Amazon Linux 2

Amazon issued ALAS advisories for all affected streams on 2026-05-26, addressing CVE-2026-43494 (e17492979319, fix part 2). On 2026-06-22, Amazon issued ALAS2023-2026-1882 and ALAS2KERNEL-5.15-2026-107 addressing CVE-2026-43502 (44b550d88b26, fix part 1) for the AL2023 kernel (6.1.x) and AL2 5.15 extra streams respectively. The same day, ALAS2KERNEL-5.10-2026-123 updated the AL2 5.10 extra kernel to 5.10.258-257.1041; while CVE-2026-43502 is not explicitly cited, the upstream 5.10.258 base carries fix part 1 as e9aefdc5c53f.

kernel6.12 and kernel6.18 are fully fixed: their upstream base versions (6.12.88, 6.18.30) already carry fix part 1, and Amazon’s advisory adds fix part 2 on top. The AL2023 kernel (6.1.x), AL2 5.15 extra, and AL2 5.10 extra streams are now also fully fixed: the 2026-06-22 updates bring the upstream base to a version (6.1.175, 5.15.209, 5.10.258) that carries fix part 1, completing the fix. The AL2 5.4 extra stream has an incomplete fix — only fix part 2 is confirmed applied; fix part 1 is absent from the EOL upstream 5.4.y branch and no ALAS advisory covers it.

Amazon Linux 2’s default Core kernel is 4.14, which predates the RDS zerocopy Tx support (0cebaccef3ac, first released in v4.17) and io_uring (v5.1). RDS is built, but neither PinTheft code path exists — AL2 Core is not affected. The AL2 5.x kernels installed via amazon-linux-extras carry both code paths; the AL2 5.4 extra stream still has an incomplete fix (fix part 2 only), reducing but not eliminating exposure on that stream.

Arch Linux

Arch Linux’s stock linux kernel ships CONFIG_RDS=m / CONFIG_RDS_TCP=m and does not blacklist the module, so it autoloads on demand. Per V12, Arch is the one common distribution where PinTheft works out of the box — it is the primary real-world target.

Fedora

Fedora builds RDS as a module (CONFIG_RDS=m) but ships it in the separate kernel-modules-extra package, which is not installed on Fedora Cloud Edition by default. Fedora also ships a modprobe.d drop-in that blacklists the RDS module. Exploitation therefore requires both installing kernel-modules-extra and overriding the blacklist — two deliberate administrative actions.

Source: Jelle van der Waa, oss-security. This is defence-in-depth, not a fix — a Fedora host that has installed kernel-modules-extra and removed the blacklist is vulnerable until the kernel is patched.

Detection

Check whether RDS is built, and how

lsmod | grep -E '^(rds|rds_tcp|rds_rdma) '

If the output is empty, check whether the kernel was built with RDS at all:

grep -E 'CONFIG_RDS\b|CONFIG_RDS_TCP|CONFIG_IO_URING' /boot/config-$(uname -r)

Interpret the output:

• # CONFIG_RDS is not set → RDS is not built — the kernel is not affected regardless of io_uring.
• CONFIG_RDS=m → loadable module — affected; the modprobe blacklist works. Check whether the module is currently loaded with lsmod.
• CONFIG_RDS=y → built in — affected and the module cannot be unloaded; the modprobe blacklist will not help.
• CONFIG_IO_URING=y is the exploit’s second ingredient. The PoC also needs io_uring_disabled=0 (the default on most distributions).

Fallback if /boot/config-* is unreadable and CONFIG_IKCONFIG_PROC=y:

zgrep -E 'CONFIG_RDS\b|CONFIG_RDS_TCP|CONFIG_IO_URING' /proc/config.gz

Public PoC

The upstream PoC is in v12-security/pocs (pintheft/poc.c):

git clone https://github.com/v12-security/pocs.git
cd pocs/pintheft
gcc -o exp poc.c
./exp

Do not run this on a system you are not authorised to test. The exploit overwrites the page cache of a readable SUID-root binary (/usr/bin/su, /usr/bin/mount, /usr/bin/passwd, /usr/bin/pkexec, …) with an ELF payload. It backs up the on-disk binary first and prints a restore command, but a corrupted SUID binary served from cache is dangerous until the cache is dropped or the host is rebooted.

Mitigation

Modprobe blacklist (when RDS is a loadable module)

Following the upstream README, block the RDS modules and remove them if loaded:

printf 'install rds /bin/false\ninstall rds_tcp /bin/false\n' > /etc/modprobe.d/pintheft.conf

rmmod rds_tcp rds 2>/dev/null || true

Verify:

lsmod | grep -E '^(rds|rds_tcp) ' && echo "STILL LOADED" || echo "Not loaded"

What this breaks: any application that uses AF_RDS sockets — RDS is used mainly by Oracle Database / Oracle RAC interconnects and some HPC workloads. Ordinary servers, desktops, and containers do not use RDS.

io_uring hardening (defence-in-depth)

The page-cache overwrite step depends on io_uring fixed buffers. Disabling io_uring blocks the demonstrated exploit chain, though it does not fix the RDS double-free itself:

sysctl -w kernel.io_uring_disabled=2

Persist it via /etc/sysctl.d/. io_uring_disabled=2 disables io_uring for all processes; value 1 restricts it to processes with CAP_SYS_ADMIN. Treat the RDS modprobe blacklist as the primary mitigation and io_uring hardening as a secondary layer.

NixOS

NixOS manages /etc/modprobe.d and /etc/sysctl.d declaratively — set the NixOS options below rather than editing those files (which are regenerated on every rebuild), then run nixos-rebuild switch. These are ordinary NixOS options: they belong in configuration.nix, or — with a flake — in any module imported by the host’s nixosConfigurations.<host> entry. The option syntax is identical either way; only the file the lines live in differs.

Block the RDS modules — this text is appended to /etc/modprobe.d/nixos.conf:

boot.extraModprobeConfig = ''
  install rds /bin/false
  install rds_tcp /bin/false
'';

Harden io_uring (defence-in-depth):

boot.kernel.sysctl."kernel.io_uring_disabled" = 2;

NixOS already blocks the unprivileged RDS autoload by default (see the NixOS row under Distribution status); the boot.extraModprobeConfig block above additionally defeats an explicit modprobe rds. Neither option unloads a module that is already loaded — reboot, or run rmmod rds_tcp rds, to clear a live one.

Built-in RDS (CONFIG_RDS=y)

If RDS is compiled in rather than modular, neither rmmod nor the modprobe blacklist help. No mainstream distribution builds RDS in; if a custom kernel does, the only options are rebuilding without CONFIG_RDS or disabling io_uring as above, until a patched kernel is available.

Risk notes

• Container hosts: the page cache is host-wide, so a container with RDS reachable can overwrite a SUID binary on the host. Apply the mitigation before running untrusted workloads on shared-kernel deployments (Docker, Kubernetes without microVM/gVisor isolation).
• CI/CD runners: self-hosted GitHub Actions, GitLab Runners, and Jenkins agents that execute untrusted code are directly in scope on affected kernels.
• Default exposure: RDS is rarely used, but it is built as a loadable module (CONFIG_RDS=m) on more distributions than the upstream PoC suggests — Debian, Proxmox, NixOS, Arch, Fedora, and Amazon Linux all ship it. RHEL-family kernels (Rocky / RHEL / AlmaLinux 8–10) are the exception and do not build it at all. Real exposure then turns on whether an unprivileged user can get the module loaded: Arch loads it on demand, whereas Debian (a kernel patch) and Fedora and NixOS (a modprobe.d blacklist of the net-pf-21 family) block the unprivileged autoload by default.
• Forensics: exploitation modifies only the in-memory page cache; the on-disk binary is untouched. Runtime detection (Falco, eBPF) or memory forensics is required — file-integrity tooling will miss it.

The in-memory corruption is transient — dropping the page cache clears it, and a reboot achieves the same:

echo 1 > /proc/sys/vm/drop_caches

Verification log

Last verified 2026-07-07.

Upstream

• CVE-2026-43494 (keyed on fix part 2, e17492979319) and CVE-2026-43502 (keyed on fix part 1, 44b550d88b26) both assigned by the Linux kernel CNA on 2026-05-21; both in cve/published/2026/ in the local vulns.git clone (confirmed via git grep -l -e 44b550d88b26 -e e17492979319 origin/master -- 'cve/published/*'). Both dyad records confirm introducing commit 0cebaccef3ac (v4.17) and list per-branch fixed versions matching the upstream table. Both named in DSA-6305-1 (2026-05-28). CVSS 3.1 score 7.8 HIGH (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) per both records; both fix commits are required for a complete fix.
• Both fix commits verified against the local netdev/net.git and stable/linux.git clones: 44b550d88b26 first appears in tag v7.1-rc3, e17492979319 in v7.1-rc4. Mainline 7.1 released 2026-06-14; 7.2-rc1 is current mainline; the linux-7.1.y stable tracking branch is at v7.1.2 with both fixes present from the initial release. The netdev/net.git queue carries unrelated RDS fixes (NULL-deref and cleanup bugs); none touches the zerocopy double-free or names PinTheft’s Fixes: commit, and none has reached a stable branch.
• Both fix commits now backported to all actively maintained stable branches. Fix part 1 (44b550d88b26): stable hash 0f5c185fc79a first in v7.0.7, 14ef6fd18db2 first in v6.18.30, 3abc8983b2ba first in v6.12.88, 21d70744e6d3 first in v6.6.140, 1e262db7675e first in v6.1.175, 46662f7dc594 first in v5.15.209, e9aefdc5c53f first in v5.10.258. Fix part 2 (e17492979319): stable hash 290e833d1acb first in v7.0.10, 640e37f58f99 first in v6.18.33, 0bbbff00a15b first in v6.12.91, 9115669faedc first in v6.6.141, d84ce1786ce4 first in v6.1.175, 03014551938a first in v5.15.209, c6e51512a784 first in v5.10.258. Current point releases: mainline 7.2-rc2, stable 7.1.3, 7.0.14 (EOL 2026-06-27), 6.18.38, 6.17.13 (EOL 2025-12-18), 6.12.95, 6.6.144, 6.1.177, 5.15.211, 5.10.260 — LTS and 7.1 branches fully fixed; the short-lived non-LTS branches between the LTS lines (6.13.x through 6.17.x, and 6.19.x) reached EOL before the disclosure and never received the backports (confirmed via stable/linux.git log); they are omitted from the upstream table except 6.17.x, kept as the base for Proxmox PVE 9; 7.0.y declared EOL 2026-06-27.
• Introducing commit 0cebaccef3ac (“rds: zerocopy Tx support.”) confirmed first released in v4.17 — every supported stable branch contains the vulnerable code.

Distributions

• Debian: CONFIG_RDS=m confirmed for Debian 11 and 13 by direct kernel-config inspection; Debian 12 carries the same setting. The RDS autoload-disable patch (MODULE_ALIAS_NETPROTO(PF_RDS) commented out in net/rds/af_rds.c) was confirmed present in the kernel patch series of the debian/latest (sid/forky), trixie, bookworm, and bullseye branches on Salsa. DSA-6305-1 (2026-05-28) fixed trixie with linux 6.12.90-2 (trixie-security pocket); explicitly covers CVE-2026-43494 (fix part 2, e17492979319); fix part 1 (44b550d88b26) was already in the upstream 6.12.90 base (first in v6.12.88), so 6.12.90-2 is fully protected against both PinTheft CVEs. DSA-6355-1 (2026-06-27) updated trixie to linux 6.12.94-1 (trixie-security); the Debian security tracker records CVE-2026-43502 (fix part 1) as fixed at 6.12.94-1. [DSA-6306-1] (2026-05-28) fixed bookworm at linux 6.1.174-1 (for CVE-2026-43503, CVE-2026-46174, CVE-2026-46300 — not CVE-2026-43494), confirming bookworm was unpatched for PinTheft (fix requires 6.1.175+). DLA-4665-1 (2026-07-03) fixed bookworm with linux 6.1.176-1 (bookworm-security); upstream 6.1.175 carries both fix commits, completing PinTheft coverage. DLA-4664-1 (2026-07-03) fixed bullseye with linux 5.10.259-1 (bullseye-security); upstream 5.10.258 carries both fix commits.
• Proxmox VE: CONFIG_RDS=m confirmed for PVE 9. Verified on a running PVE 9 host (proxmox-kernel 6.17.x) that no autoload block is present: modinfo on rds.ko shows alias: net-pf-21 intact (no Debian-style kernel patch), and modprobe -c resolves net-pf-21 to rds with no stock modprobe.d drop-in — a stock PVE 9 host autoloads rds on demand. PVE 8 confirmed the same way: rds.ko extracted from the proxmox-kernel-6.8.12-9-pve package (Proxmox bookworm repo) also carries alias: net-pf-21. Proxmox issued PSA-2026-00022-1 on 2026-05-19 acknowledging PinTheft; PSA-2026-00022-2 (2026-05-29) listed the fixed packages: proxmox-kernel-7.0.2-5-pve and proxmox-kernel-6.17.13-10-pve for PVE 9, and proxmox-kernel-6.8.12-25-pve for PVE 8.
• NixOS: both channels pin fixed kernel versions, tracked at the first-fixed pin rather than the rolling channel head: nixos-unstable pins linux_6_18 6.18.33, first fixed at channel rev 64c08a7ca051 (2026-05-23); nixos-25.11 pins linux_6_12 6.12.92, first fixed at channel rev 25f538306313 with 6.12.91 (2026-05-26). Both fixes confirmed in the upstream 6.18.y / 6.12.y branches; kernel versions verified via the local nixpkgs clone (pkgs/os-specific/linux/kernel/kernels-org.json). Later channel revisions roll these to newer already-fixed kernels (e.g. unstable to 6.18.34) — no status change. boot.modprobeConfig.useUbuntuModuleBlacklist defaults to true, confirmed in nixos/modules/system/boot/modprobe.nix.
• Rocky Linux: # CONFIG_RDS is not set confirmed for Rocky 8, 9, and 10 against the Rocky kernel configs in git.rockylinux.org (branches r8 / r9 / r10) — not affected.
• Amazon Linux: kernel build configs extracted from Amazon’s published binary kernel RPMs (2026-05-20) — CONFIG_RDS=m on AL2023 6.1 and 6.18 and on AL2 4.14 (Core) and 5.15 (extra). ALAS advisories issued 2026-05-26 for all affected streams (CVE-2026-43494 formally added to advisories 2026-06-03); fixed packages: AL2023 kernel 6.1.172-216.329, kernel6.12 6.12.88-119.157, kernel6.18 6.18.30-61.116; AL2 5.4 5.4.302-224.473, 5.10 5.10.255-253.1008, 5.15 5.15.206-144.232. The 2026-05-26 advisories list CVE-2026-43494 only. kernel6.12 and kernel6.18 are fully fixed (upstream 6.12.88 and 6.18.30 carry fix part 1; advisory adds fix part 2). On 2026-06-22, ALAS2023-2026-1882 added CVE-2026-43502 for AL2023 kernel (6.1.x) with 6.1.175-219.357 (upstream 6.1.175 carries fix part 1), completing the fix; and ALAS2KERNEL-5.15-2026-107 did the same for AL2 5.15 extra with 5.15.209-147.245 (upstream 5.15.209 carries fix part 1). Also on 2026-06-22, ALAS2KERNEL-5.10-2026-123 updated AL2 5.10 extra to 5.10.258-257.1041 (upstream 5.10.258 carries fix part 1 as e9aefdc5c53f); CVE-2026-43502 not explicitly listed in the advisory but the fix is present via upstream sync. AL2 5.4 extra still has only fix part 2 confirmed — fix part 1 absent from the EOL upstream 5.4.y branch and no ALAS covers it.
• Arch Linux: linux 7.0.10.arch1-1 (both fixes — 44b550d88b26 and e17492979319) graduated from [testing] to stable (core) on 2026-05-24; confirmed via the Arch packages page (built 2026-05-23, last updated 2026-05-24 19:27 UTC). Status updated to :white_check_mark: Fixed. CVE-2026-43494 not yet listed in the Arch security tracker.
• Fedora: module-availability behaviour per the V12 disclosure and the oss-security thread; not independently re-verified.
• EPSS: both CVEs now scored (via FIRST.org EPSS API). CVE-2026-43494 first scored 2026-05-21; CVE-2026-43502 first scored 2026-05-22. CVE-2026-43494: 0.269% (18.57th percentile); CVE-2026-43502: 0.123% (2.44th percentile) — scored 2026-07-07.

References