CVE-2024-47659

In the Linux kernel, the following vulnerability has been resolved: smack: tcp: ipv4, fix incorrect labeling Currently, Smack mirrors the label of incoming tcp/ipv4 connections: when a label 'foo' connects to a label 'bar' with tcp/ipv4, 'foo' always gets 'foo' in returned ipv4 packets. So, 1) returned packets are incorrectly labeled ('foo' instead of 'bar') 2) 'bar' can write to 'foo' without being authorized to write. Here is a scenario how to see this: * Take two machines, let's call them C and S, with active Smack in the default state (no settings, no rules, no labeled hosts, only builtin labels) * At S, add Smack rule 'foo bar w' (labels 'foo' and 'bar' are instantiated at S at this moment) * At S, at label 'bar', launch a program that listens for incoming tcp/ipv4 connections * From C, at label 'foo', connect to the listener at S. (label 'foo' is instantiated at C at this moment) Connection succeedes and works. * Send some data in both directions. * Collect network traffic of this connection. All packets in both directions are labeled with the CIPSO of the label 'foo'. Hence, label 'bar' writes to 'foo' without being authorized, and even without ever being known at C. If anybody cares: exactly the same happens with DCCP. This behavior 1st manifested in release 2.6.29.4 (see Fixes below) and it looks unintentional. At least, no explanation was provided. I changed returned packes label into the 'bar', to bring it into line with the Smack documentation claims.

• https://git.kernel.org/stable/c/0776bcf9cb6de46fdd94d10118de1cf9b05f83b9Patch
• https://git.kernel.org/stable/c/0aea09e82eafa50a373fc8a4b84c1d4734751e2cPatch
• https://git.kernel.org/stable/c/2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550Patch
• https://git.kernel.org/stable/c/4be9fd15c3c88775bdf6fa37acabe6de85beebffPatch
• https://git.kernel.org/stable/c/5b4b304f196c070342e32a4752e1fa2e22fc0671Patch
• https://git.kernel.org/stable/c/a948ec993541db4ef392b555c37a1186f4d61670Patch
• https://git.kernel.org/stable/c/d3703fa94116fed91f64c7d1c7d284fb4369070fPatch
• https://git.kernel.org/stable/c/d3f56c653c65f170b172d3c23120bc64ada645d8Patch
• https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Published

Oct 9, 2024

Last Modified

Aug 4, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2024-47653This vulnerability exists in Shilpi Client Dashboard due to …6.5
• CVE-2024-47654This vulnerability exists in Shilpi Client Dashboard due to …7.5
• CVE-2024-47655This vulnerability exists in the Shilpi Client Dashboard due…8.8
• CVE-2024-47656This vulnerability exists in Shilpi Client Dashboard due to …9.8
• CVE-2024-47657This vulnerability exists in the Shilpi Net Back Office due …6.5
• CVE-2024-47658In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-4766Different techniques existed to obscure the fullscreen notif…4.3
• CVE-2024-47660In the Linux kernel, the following vulnerability has been re…4.7
• CVE-2024-47661In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-47662In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-47663In the Linux kernel, the following vulnerability has been re…5.5
• CVE-2024-47664In the Linux kernel, the following vulnerability has been re…5.5