Skip to content
VulniPulse
High7.0Red Hat Linux

High [CVE-2026-74434] Don't move a peeked OOB message onto the pending queue

This high-severity Red Hat Linux advisory covers CVE-2026-74434 affecting Red Hat Enterprise Linux 10, Red Hat package: kernel.

CVE-2026-74434 Published Aug 15, 2026Updated by vendor Aug 15, 2026
Affected products & platforms
Red Hat LinuxLinux Kernel
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in the Linux kernel's rxrpc subsystem. When an out-of-band (OOB) message is read using the MSG_PEEK flag in the rxrpc_recvmsg_oob() function, the message is incorrectly left on one queue while also being added to another.

This can lead to the message being freed twice when the socket is closed, resulting in memory corruption and a use-after-free vulnerability. A local attacker could exploit this to cause system instability or potentially execute arbitrary code.

Red Hat severity: Important — CVSS 7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Weakness: CWE-1341.

Affected Red Hat products: Red Hat Enterprise Linux 10. Red Hat does not currently list a fixing RHSA for this CVE.

Affected products named by the advisory: Red Hat package: kernel.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.