8.8
Advisory Published
Updated

CVE-2024-47659: smack: tcp: ipv4, fix incorrect labeling

First published: Wed Oct 09 2024(Updated: )

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.

Credit: 416baaa9-dc9f-4396-8d5f-8c081fb06d67 416baaa9-dc9f-4396-8d5f-8c081fb06d67

Affected SoftwareAffected VersionHow to fix
Linux Kernel<4.19.322
Linux Kernel>=4.20<5.4.284
Linux Kernel>=5.5<5.10.226
Linux Kernel>=5.11<5.15.167
Linux Kernel>=5.16<6.1.109
Linux Kernel>=6.2<6.6.50
Linux Kernel>=6.7<6.10.9
debian/linux<=5.10.223-1<=5.10.234-1
6.1.129-1
6.1.128-1
6.12.21-1
debian/linux-6.1
6.1.129-1~deb11u1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of CVE-2024-47659?

    CVE-2024-47659 has been classified as a medium severity vulnerability.

  • How do I fix CVE-2024-47659?

    To resolve CVE-2024-47659, upgrade to the patched versions of the affected Linux kernel packages as specified in the advisory.

  • Which Linux kernel versions are affected by CVE-2024-47659?

    CVE-2024-47659 affects Linux kernel versions from 5.10 and before up to 6.10.

  • What specific issue does CVE-2024-47659 address in the Linux kernel?

    CVE-2024-47659 addresses an issue with incorrect labeling in Smack for incoming tcp/ipv4 connections.

  • Is my system vulnerable to CVE-2024-47659?

    Check if your system is running an affected version of the Linux kernel that is listed for CVE-2024-47659.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203