Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

Description

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.

Timeline

  1. ID reserved

    By Linux

  2. · 9 days later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47659, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
NVDNVD · Modified3.1High8.8CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.78% · top 43% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.1.

Affected products

  • Linux · Linux

    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < d3f56c653c65f170b172d3c23120bc64ada645d8
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < 5b4b304f196c070342e32a4752e1fa2e22fc0671
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < a948ec993541db4ef392b555c37a1186f4d61670
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < 0aea09e82eafa50a373fc8a4b84c1d4734751e2c
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < 0776bcf9cb6de46fdd94d10118de1cf9b05f83b9
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < 4be9fd15c3c88775bdf6fa37acabe6de85beebff
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < d3703fa94116fed91f64c7d1c7d284fb4369070f
    • affected 07feee8f812f7327a46186f7604df312c8c81962 – < 2fe209d0ad2e2729f7e22b9b31a86cc3ff0db550
  • Linux · Linux

    • affected 2.6.30
    • unaffected < 2.6.30
    • unaffected 4.19.322 – ≤ 4.19.*
    • unaffected 5.4.284 – ≤ 5.4.*
    • unaffected 5.10.226 – ≤ 5.10.*
    • unaffected 5.15.167 – ≤ 5.15.*
    • unaffected 6.1.109 – ≤ 6.1.*
    • unaffected 6.6.50 – ≤ 6.6.*
    • unaffected 6.10.9 – ≤ 6.10.*
    • unaffected 6.11 – ≤ *

References

References9

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47659 badge
[![CVE-2024-47659](https://cveledger.app/badge/CVE-2024-47659.svg)](https://cveledger.app/cve/CVE-2024-47659)

Record last updated .