{
  "cveId": "CVE-2024-47659",
  "url": "https://patchblox.com/security/cve/CVE-2024-47659",
  "summary": "CVE-2024-47659 is fixed in linux on 1 platform, first by DEBIAN-CVE-2024-47659, released October 9, 2024. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  smack: tcp: ipv4, fix incorrect labeling  Curren...",
  "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 \u0027foo\u0027 connects to a label \u0027bar\u0027 with tcp/ipv4, \u0027foo\u0027 always gets \u0027foo\u0027 in returned ipv4 packets. So, 1) returned packets are incorrectly labeled (\u0027foo\u0027 instead of \u0027bar\u0027) 2) \u0027bar\u0027 can write to \u0027foo\u0027 without being authorized to write.  Here is a scenario how to see this:  * Take two machines, let\u0027s 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 \u0027foo bar w\u0027    (labels \u0027foo\u0027 and \u0027bar\u0027 are instantiated at S at this moment)  * At S, at label \u0027bar\u0027, launch a program    that listens for incoming tcp/ipv4 connections  * From C, at label \u0027foo\u0027, connect to the listener at S.    (label \u0027foo\u0027 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 \u0027foo\u0027. Hence, label \u0027bar\u0027 writes to \u0027foo\u0027 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 \u0027bar\u0027, to bring it into line with the Smack documentation claims.",
  "published": "2024-10-09T14:15:07Z",
  "severity": "high",
  "cvss": 8.8,
  "cvssVector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00775,
  "epssPercentile": 0.56023,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.112-1",
      "fix": "DEBIAN-CVE-2024-47659",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47659",
      "released": "2024-10-09T14:15:07Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.10.9-1",
      "fix": "DEBIAN-CVE-2024-47659",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47659",
      "released": "2024-10-09T14:15:07Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.10.9-1",
      "fix": "DEBIAN-CVE-2024-47659",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2024-47659",
      "released": "2024-10-09T14:15:07Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}