CVE-2024-56633 (GCVE-0-2024-56633)

Vulnerability from cvelistv5 – Published: 2024-12-27 15:02 – Updated: 2026-05-11 20:56
VLAI
Title
tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg
Summary
In the Linux kernel, the following vulnerability has been resolved: tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg The current sk memory accounting logic in __SK_REDIRECT is pre-uncharging tosend bytes, which is either msg->sg.size or a smaller value apply_bytes. Potential problems with this strategy are as follows: - If the actual sent bytes are smaller than tosend, we need to charge some bytes back, as in line 487, which is okay but seems not clean. - When tosend is set to apply_bytes, as in line 417, and (ret < 0), we may miss uncharging (msg->sg.size - apply_bytes) bytes. [...] 415 tosend = msg->sg.size; 416 if (psock->apply_bytes && psock->apply_bytes < tosend) 417 tosend = psock->apply_bytes; [...] 443 sk_msg_return(sk, msg, tosend); 444 release_sock(sk); 446 origsize = msg->sg.size; 447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress, 448 msg, tosend, flags); 449 sent = origsize - msg->sg.size; [...] 454 lock_sock(sk); 455 if (unlikely(ret < 0)) { 456 int free = sk_msg_free_nocharge(sk, msg); 458 if (!cork) 459 *copied -= free; 460 } [...] 487 if (eval == __SK_REDIRECT) 488 sk_mem_charge(sk, tosend - sent); [...] When running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply, the following warning will be reported: ------------[ cut here ]------------ WARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0 Modules linked in: CPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Workqueue: events sk_psock_destroy RIP: 0010:inet_sock_destruct+0x190/0x1a0 RSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206 RAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800 RDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900 RBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0 R10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400 R13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100 FS: 0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Call Trace: <TASK> ? __warn+0x89/0x130 ? inet_sock_destruct+0x190/0x1a0 ? report_bug+0xfc/0x1e0 ? handle_bug+0x5c/0xa0 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? inet_sock_destruct+0x190/0x1a0 __sk_destruct+0x25/0x220 sk_psock_destroy+0x2b2/0x310 process_scheduled_works+0xa3/0x3e0 worker_thread+0x117/0x240 ? __pfx_worker_thread+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_from_fork+0x31/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30 </TASK> ---[ end trace 0000000000000000 ]--- In __SK_REDIRECT, a more concise way is delaying the uncharging after sent bytes are finalized, and uncharge this value. When (ret < 0), we shall invoke sk_msg_free. Same thing happens in case __SK_DROP, when tosend is set to apply_bytes, we may miss uncharging (msg->sg.size - apply_bytes) bytes. The same warning will be reported in selftest. [...] 468 case __SK_DROP: 469 default: 470 sk_msg_free_partial(sk, msg, tosend); 471 sk_msg_apply_bytes(psock, tosend); 472 *copied -= (tosend + delta); 473 return -EACCES; [...] So instead of sk_msg_free_partial we can do sk_msg_free here.
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Assigner
References
Impacted products
Vendor Product Version
Linux Linux Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < 905d82e6e77d16ec3e089c92b7b59a14899dfc1a (git)
Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < dbedc7e142df5ea238a46fdd7462c1c42cd36a10 (git)
Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < 0d6cd1151e26fc7c2d5daa85e8984aaa685a1a12 (git)
Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < 456f08d24afa51b5eb816c42e4ca1c44a247bd42 (git)
Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < 206d56f41a1509cadd06e2178c26cb830e45057d (git)
Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < 5c9e3bb43a354a2245caebbbbb4a5b8c034fdd56 (git)
Affected: 604326b41a6fb9b4a78b6179335decee0365cd8c , < ca70b8baf2bd125b2a4d96e76db79375c07d7ff2 (git)
Create a notification for this product.
Linux Linux Affected: 4.20
Unaffected: 0 , < 4.20 (semver)
Unaffected: 5.4.287 , ≤ 5.4.* (semver)
Unaffected: 5.10.231 , ≤ 5.10.* (semver)
Unaffected: 5.15.174 , ≤ 5.15.* (semver)
Unaffected: 6.1.120 , ≤ 6.1.* (semver)
Unaffected: 6.6.66 , ≤ 6.6.* (semver)
Unaffected: 6.12.5 , ≤ 6.12.* (semver)
Unaffected: 6.13 , ≤ * (original_commit_for_fix)
Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "providerMetadata": {
          "dateUpdated": "2025-11-03T20:51:30.092Z",
          "orgId": "af854a3a-2127-422b-91ae-364da2661108",
          "shortName": "CVE"
        },
        "references": [
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html"
          },
          {
            "url": "https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html"
          }
        ],
        "title": "CVE Program Container"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "net/ipv4/tcp_bpf.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "905d82e6e77d16ec3e089c92b7b59a14899dfc1a",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            },
            {
              "lessThan": "dbedc7e142df5ea238a46fdd7462c1c42cd36a10",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            },
            {
              "lessThan": "0d6cd1151e26fc7c2d5daa85e8984aaa685a1a12",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            },
            {
              "lessThan": "456f08d24afa51b5eb816c42e4ca1c44a247bd42",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            },
            {
              "lessThan": "206d56f41a1509cadd06e2178c26cb830e45057d",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            },
            {
              "lessThan": "5c9e3bb43a354a2245caebbbbb4a5b8c034fdd56",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            },
            {
              "lessThan": "ca70b8baf2bd125b2a4d96e76db79375c07d7ff2",
              "status": "affected",
              "version": "604326b41a6fb9b4a78b6179335decee0365cd8c",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "net/ipv4/tcp_bpf.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "4.20"
            },
            {
              "lessThan": "4.20",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.4.*",
              "status": "unaffected",
              "version": "5.4.287",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.10.*",
              "status": "unaffected",
              "version": "5.10.231",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "5.15.*",
              "status": "unaffected",
              "version": "5.15.174",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.1.*",
              "status": "unaffected",
              "version": "6.1.120",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.6.*",
              "status": "unaffected",
              "version": "6.6.66",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.12.*",
              "status": "unaffected",
              "version": "6.12.5",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.13",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.4.287",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.10.231",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.15.174",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1.120",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.6.66",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.12.5",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.13",
                  "versionStartIncluding": "4.20",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ntcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg\n\nThe current sk memory accounting logic in __SK_REDIRECT is pre-uncharging\ntosend bytes, which is either msg-\u003esg.size or a smaller value apply_bytes.\n\nPotential problems with this strategy are as follows:\n\n- If the actual sent bytes are smaller than tosend, we need to charge some\n  bytes back, as in line 487, which is okay but seems not clean.\n\n- When tosend is set to apply_bytes, as in line 417, and (ret \u003c 0), we may\n  miss uncharging (msg-\u003esg.size - apply_bytes) bytes.\n\n[...]\n415 tosend = msg-\u003esg.size;\n416 if (psock-\u003eapply_bytes \u0026\u0026 psock-\u003eapply_bytes \u003c tosend)\n417   tosend = psock-\u003eapply_bytes;\n[...]\n443 sk_msg_return(sk, msg, tosend);\n444 release_sock(sk);\n446 origsize = msg-\u003esg.size;\n447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress,\n448                             msg, tosend, flags);\n449 sent = origsize - msg-\u003esg.size;\n[...]\n454 lock_sock(sk);\n455 if (unlikely(ret \u003c 0)) {\n456   int free = sk_msg_free_nocharge(sk, msg);\n458   if (!cork)\n459     *copied -= free;\n460 }\n[...]\n487 if (eval == __SK_REDIRECT)\n488   sk_mem_charge(sk, tosend - sent);\n[...]\n\nWhen running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply,\nthe following warning will be reported:\n\n------------[ cut here ]------------\nWARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0\nModules linked in:\nCPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\nWorkqueue: events sk_psock_destroy\nRIP: 0010:inet_sock_destruct+0x190/0x1a0\nRSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206\nRAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800\nRDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900\nRBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0\nR10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400\nR13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100\nFS:  0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\nCR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\nPKRU: 55555554\nCall Trace:\n\u003cTASK\u003e\n? __warn+0x89/0x130\n? inet_sock_destruct+0x190/0x1a0\n? report_bug+0xfc/0x1e0\n? handle_bug+0x5c/0xa0\n? exc_invalid_op+0x17/0x70\n? asm_exc_invalid_op+0x1a/0x20\n? inet_sock_destruct+0x190/0x1a0\n__sk_destruct+0x25/0x220\nsk_psock_destroy+0x2b2/0x310\nprocess_scheduled_works+0xa3/0x3e0\nworker_thread+0x117/0x240\n? __pfx_worker_thread+0x10/0x10\nkthread+0xcf/0x100\n? __pfx_kthread+0x10/0x10\nret_from_fork+0x31/0x40\n? __pfx_kthread+0x10/0x10\nret_from_fork_asm+0x1a/0x30\n\u003c/TASK\u003e\n---[ end trace 0000000000000000 ]---\n\nIn __SK_REDIRECT, a more concise way is delaying the uncharging after sent\nbytes are finalized, and uncharge this value. When (ret \u003c 0), we shall\ninvoke sk_msg_free.\n\nSame thing happens in case __SK_DROP, when tosend is set to apply_bytes,\nwe may miss uncharging (msg-\u003esg.size - apply_bytes) bytes. The same\nwarning will be reported in selftest.\n\n[...]\n468 case __SK_DROP:\n469 default:\n470 sk_msg_free_partial(sk, msg, tosend);\n471 sk_msg_apply_bytes(psock, tosend);\n472 *copied -= (tosend + delta);\n473 return -EACCES;\n[...]\n\nSo instead of sk_msg_free_partial we can do sk_msg_free here."
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-05-11T20:56:15.744Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/905d82e6e77d16ec3e089c92b7b59a14899dfc1a"
        },
        {
          "url": "https://git.kernel.org/stable/c/dbedc7e142df5ea238a46fdd7462c1c42cd36a10"
        },
        {
          "url": "https://git.kernel.org/stable/c/0d6cd1151e26fc7c2d5daa85e8984aaa685a1a12"
        },
        {
          "url": "https://git.kernel.org/stable/c/456f08d24afa51b5eb816c42e4ca1c44a247bd42"
        },
        {
          "url": "https://git.kernel.org/stable/c/206d56f41a1509cadd06e2178c26cb830e45057d"
        },
        {
          "url": "https://git.kernel.org/stable/c/5c9e3bb43a354a2245caebbbbb4a5b8c034fdd56"
        },
        {
          "url": "https://git.kernel.org/stable/c/ca70b8baf2bd125b2a4d96e76db79375c07d7ff2"
        }
      ],
      "title": "tcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2024-56633",
    "datePublished": "2024-12-27T15:02:31.273Z",
    "dateReserved": "2024-12-27T15:00:39.838Z",
    "dateUpdated": "2026-05-11T20:56:15.744Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2024-56633",
      "date": "2026-06-07",
      "epss": "0.00022",
      "percentile": "0.0656"
    },
    "fkie_nvd": {
      "descriptions": "[{\"lang\": \"en\", \"value\": \"In the Linux kernel, the following vulnerability has been resolved:\\n\\ntcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg\\n\\nThe current sk memory accounting logic in __SK_REDIRECT is pre-uncharging\\ntosend bytes, which is either msg-\u003esg.size or a smaller value apply_bytes.\\n\\nPotential problems with this strategy are as follows:\\n\\n- If the actual sent bytes are smaller than tosend, we need to charge some\\n  bytes back, as in line 487, which is okay but seems not clean.\\n\\n- When tosend is set to apply_bytes, as in line 417, and (ret \u003c 0), we may\\n  miss uncharging (msg-\u003esg.size - apply_bytes) bytes.\\n\\n[...]\\n415 tosend = msg-\u003esg.size;\\n416 if (psock-\u003eapply_bytes \u0026\u0026 psock-\u003eapply_bytes \u003c tosend)\\n417   tosend = psock-\u003eapply_bytes;\\n[...]\\n443 sk_msg_return(sk, msg, tosend);\\n444 release_sock(sk);\\n446 origsize = msg-\u003esg.size;\\n447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress,\\n448                             msg, tosend, flags);\\n449 sent = origsize - msg-\u003esg.size;\\n[...]\\n454 lock_sock(sk);\\n455 if (unlikely(ret \u003c 0)) {\\n456   int free = sk_msg_free_nocharge(sk, msg);\\n458   if (!cork)\\n459     *copied -= free;\\n460 }\\n[...]\\n487 if (eval == __SK_REDIRECT)\\n488   sk_mem_charge(sk, tosend - sent);\\n[...]\\n\\nWhen running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply,\\nthe following warning will be reported:\\n\\n------------[ cut here ]------------\\nWARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0\\nModules linked in:\\nCPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\\nWorkqueue: events sk_psock_destroy\\nRIP: 0010:inet_sock_destruct+0x190/0x1a0\\nRSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206\\nRAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800\\nRDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900\\nRBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0\\nR10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400\\nR13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100\\nFS:  0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000\\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\\nCR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0\\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\\nPKRU: 55555554\\nCall Trace:\\n\u003cTASK\u003e\\n? __warn+0x89/0x130\\n? inet_sock_destruct+0x190/0x1a0\\n? report_bug+0xfc/0x1e0\\n? handle_bug+0x5c/0xa0\\n? exc_invalid_op+0x17/0x70\\n? asm_exc_invalid_op+0x1a/0x20\\n? inet_sock_destruct+0x190/0x1a0\\n__sk_destruct+0x25/0x220\\nsk_psock_destroy+0x2b2/0x310\\nprocess_scheduled_works+0xa3/0x3e0\\nworker_thread+0x117/0x240\\n? __pfx_worker_thread+0x10/0x10\\nkthread+0xcf/0x100\\n? __pfx_kthread+0x10/0x10\\nret_from_fork+0x31/0x40\\n? __pfx_kthread+0x10/0x10\\nret_from_fork_asm+0x1a/0x30\\n\u003c/TASK\u003e\\n---[ end trace 0000000000000000 ]---\\n\\nIn __SK_REDIRECT, a more concise way is delaying the uncharging after sent\\nbytes are finalized, and uncharge this value. When (ret \u003c 0), we shall\\ninvoke sk_msg_free.\\n\\nSame thing happens in case __SK_DROP, when tosend is set to apply_bytes,\\nwe may miss uncharging (msg-\u003esg.size - apply_bytes) bytes. The same\\nwarning will be reported in selftest.\\n\\n[...]\\n468 case __SK_DROP:\\n469 default:\\n470 sk_msg_free_partial(sk, msg, tosend);\\n471 sk_msg_apply_bytes(psock, tosend);\\n472 *copied -= (tosend + delta);\\n473 return -EACCES;\\n[...]\\n\\nSo instead of sk_msg_free_partial we can do sk_msg_free here.\"}, {\"lang\": \"es\", \"value\": \"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tcp_bpf: Arreglar la l\\u00f3gica sk_mem_uncharge en tcp_bpf_sendmsg La l\\u00f3gica actual de contabilidad de memoria sk en __SK_REDIRECT est\\u00e1 pre-descargando bytes tosend, que es msg-\u0026gt;sg.size o un valor menor apply_bytes. Los problemas potenciales con esta estrategia son los siguientes: - Si los bytes enviados reales son m\\u00e1s peque\\u00f1os que tosend, necesitamos cargar algunos bytes de vuelta, como en la l\\u00ednea 487, lo cual est\\u00e1 bien pero no parece limpio. - Cuando tosend est\\u00e1 configurado en apply_bytes, como en la l\\u00ednea 417, y (ret \u0026lt; 0), podemos perder la descarga de (msg-\u0026gt;sg.size - apply_bytes) bytes. [...] 415 tosend = msg-\u0026gt;sg.size; 416 si (psock-\u0026gt;aplicar_bytes \u0026amp;\u0026amp; psock-\u0026gt;aplicar_bytes \u0026lt; para enviar) 417 para enviar = psock-\u0026gt;aplicar_bytes; [...] 443 sk_msg_return(sk, msg, para enviar); 444 release_sock(sk); 446 tama\\u00f1o original = msg-\u0026gt;sg.tama\\u00f1o; 447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress, 448 msg, para enviar, indicadores); 449 enviado = tama\\u00f1o original - msg-\u0026gt;sg.tama\\u00f1o; [...] 454 bloqueo_sock(sk); 455 si (improbable(ret \u0026lt; 0)) { 456 int libre = sk_msg_libre_sincarga(sk, msg); 458 si (!corcho) 459 *copiado -= libre; 460 } [...] 487 si (eval == __SK_REDIRECT) 488 sk_mem_charge(sk, tosend - enviado); [...] Al ejecutar la prueba autom\\u00e1tica test_txmsg_redir_wait_sndmem con txmsg_apply, se informar\\u00e1 la siguiente advertencia: ------------[ cortar aqu\\u00ed ]------------ ADVERTENCIA: CPU: 6 PID: 57 en net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0 M\\u00f3dulos vinculados: CPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 No contaminado 6.12.0-rc1.bm.1-amd64+ #43 Nombre del hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Cola de trabajo: eventos sk_psock_destroy RIP: 0010:inet_sock_destruct+0x190/0x1a0 RSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206 RAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800 RDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900 RBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0 R10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400 R13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: muerto000000000100 FS: 000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0 DR0: 00000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Seguimiento de llamadas:  ? __warn+0x89/0x130 ? inet_sock_destruct+0x190/0x1a0 ? report_bug+0xfc/0x1e0 ? handle_bug+0x5c/0xa0 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? inet_sock_destruct+0x190/0x1a0 __sk_destruct+0x25/0x220 sk_psock_destroy+0x2b2/0x310 proceso_trabajos_programados+0xa3/0x3e0 subproceso_trabajador+0x117/0x240 ? __pfx_worker_thread+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_de_bifurcaci\\u00f3n+0x31/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30  ---[ fin del seguimiento 000000000000000 ]--- En __SK_REDIRECT, una forma m\\u00e1s concisa es retrasar la descarga despu\\u00e9s de que se finalizan los bytes enviados y descargar este valor. Cuando (ret \u0026lt; 0), invocaremos sk_msg_free. Lo mismo sucede en el caso __SK_DROP, cuando tosend se establece en apply_bytes, podemos perder la descarga de (msg-\u0026gt;sg.size - apply_bytes) bytes. La misma advertencia se informar\\u00e1 en la autoprueba. [...] 468 caso __SK_DROP: 469 predeterminado: 470 sk_msg_free_partial(sk, msg, tosend); 471 sk_msg_apply_bytes(psock, tosend); 472 *copied -= (tosend + delta); 473 return -EACCES; [...] Entonces, en lugar de sk_msg_free_partial, podemos hacer sk_msg_free aqu\\u00ed.\"}]",
      "id": "CVE-2024-56633",
      "lastModified": "2024-12-27T15:15:22.933",
      "published": "2024-12-27T15:15:22.933",
      "references": "[{\"url\": \"https://git.kernel.org/stable/c/0d6cd1151e26fc7c2d5daa85e8984aaa685a1a12\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/206d56f41a1509cadd06e2178c26cb830e45057d\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/456f08d24afa51b5eb816c42e4ca1c44a247bd42\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/5c9e3bb43a354a2245caebbbbb4a5b8c034fdd56\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/905d82e6e77d16ec3e089c92b7b59a14899dfc1a\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/ca70b8baf2bd125b2a4d96e76db79375c07d7ff2\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}, {\"url\": \"https://git.kernel.org/stable/c/dbedc7e142df5ea238a46fdd7462c1c42cd36a10\", \"source\": \"416baaa9-dc9f-4396-8d5f-8c081fb06d67\"}]",
      "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
      "vulnStatus": "Awaiting Analysis"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2024-56633\",\"sourceIdentifier\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"published\":\"2024-12-27T15:15:22.933\",\"lastModified\":\"2025-11-03T21:18:11.540\",\"vulnStatus\":\"Modified\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"In the Linux kernel, the following vulnerability has been resolved:\\n\\ntcp_bpf: Fix the sk_mem_uncharge logic in tcp_bpf_sendmsg\\n\\nThe current sk memory accounting logic in __SK_REDIRECT is pre-uncharging\\ntosend bytes, which is either msg-\u003esg.size or a smaller value apply_bytes.\\n\\nPotential problems with this strategy are as follows:\\n\\n- If the actual sent bytes are smaller than tosend, we need to charge some\\n  bytes back, as in line 487, which is okay but seems not clean.\\n\\n- When tosend is set to apply_bytes, as in line 417, and (ret \u003c 0), we may\\n  miss uncharging (msg-\u003esg.size - apply_bytes) bytes.\\n\\n[...]\\n415 tosend = msg-\u003esg.size;\\n416 if (psock-\u003eapply_bytes \u0026\u0026 psock-\u003eapply_bytes \u003c tosend)\\n417   tosend = psock-\u003eapply_bytes;\\n[...]\\n443 sk_msg_return(sk, msg, tosend);\\n444 release_sock(sk);\\n446 origsize = msg-\u003esg.size;\\n447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress,\\n448                             msg, tosend, flags);\\n449 sent = origsize - msg-\u003esg.size;\\n[...]\\n454 lock_sock(sk);\\n455 if (unlikely(ret \u003c 0)) {\\n456   int free = sk_msg_free_nocharge(sk, msg);\\n458   if (!cork)\\n459     *copied -= free;\\n460 }\\n[...]\\n487 if (eval == __SK_REDIRECT)\\n488   sk_mem_charge(sk, tosend - sent);\\n[...]\\n\\nWhen running the selftest test_txmsg_redir_wait_sndmem with txmsg_apply,\\nthe following warning will be reported:\\n\\n------------[ cut here ]------------\\nWARNING: CPU: 6 PID: 57 at net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0\\nModules linked in:\\nCPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 Not tainted 6.12.0-rc1.bm.1-amd64+ #43\\nHardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014\\nWorkqueue: events sk_psock_destroy\\nRIP: 0010:inet_sock_destruct+0x190/0x1a0\\nRSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206\\nRAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800\\nRDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900\\nRBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0\\nR10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400\\nR13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: dead000000000100\\nFS:  0000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000\\nCS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\\nCR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0\\nDR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000\\nDR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400\\nPKRU: 55555554\\nCall Trace:\\n\u003cTASK\u003e\\n? __warn+0x89/0x130\\n? inet_sock_destruct+0x190/0x1a0\\n? report_bug+0xfc/0x1e0\\n? handle_bug+0x5c/0xa0\\n? exc_invalid_op+0x17/0x70\\n? asm_exc_invalid_op+0x1a/0x20\\n? inet_sock_destruct+0x190/0x1a0\\n__sk_destruct+0x25/0x220\\nsk_psock_destroy+0x2b2/0x310\\nprocess_scheduled_works+0xa3/0x3e0\\nworker_thread+0x117/0x240\\n? __pfx_worker_thread+0x10/0x10\\nkthread+0xcf/0x100\\n? __pfx_kthread+0x10/0x10\\nret_from_fork+0x31/0x40\\n? __pfx_kthread+0x10/0x10\\nret_from_fork_asm+0x1a/0x30\\n\u003c/TASK\u003e\\n---[ end trace 0000000000000000 ]---\\n\\nIn __SK_REDIRECT, a more concise way is delaying the uncharging after sent\\nbytes are finalized, and uncharge this value. When (ret \u003c 0), we shall\\ninvoke sk_msg_free.\\n\\nSame thing happens in case __SK_DROP, when tosend is set to apply_bytes,\\nwe may miss uncharging (msg-\u003esg.size - apply_bytes) bytes. The same\\nwarning will be reported in selftest.\\n\\n[...]\\n468 case __SK_DROP:\\n469 default:\\n470 sk_msg_free_partial(sk, msg, tosend);\\n471 sk_msg_apply_bytes(psock, tosend);\\n472 *copied -= (tosend + delta);\\n473 return -EACCES;\\n[...]\\n\\nSo instead of sk_msg_free_partial we can do sk_msg_free here.\"},{\"lang\":\"es\",\"value\":\"En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: tcp_bpf: Arreglar la l\u00f3gica sk_mem_uncharge en tcp_bpf_sendmsg La l\u00f3gica actual de contabilidad de memoria sk en __SK_REDIRECT est\u00e1 pre-descargando bytes tosend, que es msg-\u0026gt;sg.size o un valor menor apply_bytes. Los problemas potenciales con esta estrategia son los siguientes: - Si los bytes enviados reales son m\u00e1s peque\u00f1os que tosend, necesitamos cargar algunos bytes de vuelta, como en la l\u00ednea 487, lo cual est\u00e1 bien pero no parece limpio. - Cuando tosend est\u00e1 configurado en apply_bytes, como en la l\u00ednea 417, y (ret \u0026lt; 0), podemos perder la descarga de (msg-\u0026gt;sg.size - apply_bytes) bytes. [...] 415 tosend = msg-\u0026gt;sg.size; 416 si (psock-\u0026gt;aplicar_bytes \u0026amp;\u0026amp; psock-\u0026gt;aplicar_bytes \u0026lt; para enviar) 417 para enviar = psock-\u0026gt;aplicar_bytes; [...] 443 sk_msg_return(sk, msg, para enviar); 444 release_sock(sk); 446 tama\u00f1o original = msg-\u0026gt;sg.tama\u00f1o; 447 ret = tcp_bpf_sendmsg_redir(sk_redir, redir_ingress, 448 msg, para enviar, indicadores); 449 enviado = tama\u00f1o original - msg-\u0026gt;sg.tama\u00f1o; [...] 454 bloqueo_sock(sk); 455 si (improbable(ret \u0026lt; 0)) { 456 int libre = sk_msg_libre_sincarga(sk, msg); 458 si (!corcho) 459 *copiado -= libre; 460 } [...] 487 si (eval == __SK_REDIRECT) 488 sk_mem_charge(sk, tosend - enviado); [...] Al ejecutar la prueba autom\u00e1tica test_txmsg_redir_wait_sndmem con txmsg_apply, se informar\u00e1 la siguiente advertencia: ------------[ cortar aqu\u00ed ]------------ ADVERTENCIA: CPU: 6 PID: 57 en net/ipv4/af_inet.c:156 inet_sock_destruct+0x190/0x1a0 M\u00f3dulos vinculados: CPU: 6 UID: 0 PID: 57 Comm: kworker/6:0 No contaminado 6.12.0-rc1.bm.1-amd64+ #43 Nombre del hardware: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 Cola de trabajo: eventos sk_psock_destroy RIP: 0010:inet_sock_destruct+0x190/0x1a0 RSP: 0018:ffffad0a8021fe08 EFLAGS: 00010206 RAX: 0000000000000011 RBX: ffff9aab4475b900 RCX: ffff9aab481a0800 RDX: 0000000000000303 RSI: 0000000000000011 RDI: ffff9aab4475b900 RBP: ffff9aab4475b990 R08: 0000000000000000 R09: ffff9aab40050ec0 R10: 0000000000000000 R11: ffff9aae6fdb1d01 R12: ffff9aab49c60400 R13: ffff9aab49c60598 R14: ffff9aab49c60598 R15: muerto000000000100 FS: 000000000000000(0000) GS:ffff9aae6fd80000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffec7e47bd8 CR3: 00000001a1a1c004 CR4: 0000000000770ef0 DR0: 00000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 PKRU: 55555554 Seguimiento de llamadas:  ? __warn+0x89/0x130 ? inet_sock_destruct+0x190/0x1a0 ? report_bug+0xfc/0x1e0 ? handle_bug+0x5c/0xa0 ? exc_invalid_op+0x17/0x70 ? asm_exc_invalid_op+0x1a/0x20 ? inet_sock_destruct+0x190/0x1a0 __sk_destruct+0x25/0x220 sk_psock_destroy+0x2b2/0x310 proceso_trabajos_programados+0xa3/0x3e0 subproceso_trabajador+0x117/0x240 ? __pfx_worker_thread+0x10/0x10 kthread+0xcf/0x100 ? __pfx_kthread+0x10/0x10 ret_de_bifurcaci\u00f3n+0x31/0x40 ? __pfx_kthread+0x10/0x10 ret_from_fork_asm+0x1a/0x30  ---[ fin del seguimiento 000000000000000 ]--- En __SK_REDIRECT, una forma m\u00e1s concisa es retrasar la descarga despu\u00e9s de que se finalizan los bytes enviados y descargar este valor. Cuando (ret \u0026lt; 0), invocaremos sk_msg_free. Lo mismo sucede en el caso __SK_DROP, cuando tosend se establece en apply_bytes, podemos perder la descarga de (msg-\u0026gt;sg.size - apply_bytes) bytes. La misma advertencia se informar\u00e1 en la autoprueba. [...] 468 caso __SK_DROP: 469 predeterminado: 470 sk_msg_free_partial(sk, msg, tosend); 471 sk_msg_apply_bytes(psock, tosend); 472 *copied -= (tosend + delta); 473 return -EACCES; [...] Entonces, en lugar de sk_msg_free_partial, podemos hacer sk_msg_free aqu\u00ed.\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":7.8,\"baseSeverity\":\"HIGH\",\"attackVector\":\"LOCAL\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"LOW\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":1.8,\"impactScore\":5.9}]},\"weaknesses\":[{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"description\":[{\"lang\":\"en\",\"value\":\"NVD-CWE-noinfo\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"4.20\",\"versionEndExcluding\":\"5.4.287\",\"matchCriteriaId\":\"E4B15788-D35E-4E5B-A9C0-070AE3729B34\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.5\",\"versionEndExcluding\":\"5.10.231\",\"matchCriteriaId\":\"B5C644CC-2BD7-4E32-BC54-8DCC7ABE9935\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.11\",\"versionEndExcluding\":\"5.15.174\",\"matchCriteriaId\":\"419FD073-1517-4FD5-8158-F94BC68A1E89\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"5.16\",\"versionEndExcluding\":\"6.1.120\",\"matchCriteriaId\":\"09AC6122-E2A4-40FE-9D33-268A1B2EC265\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.2\",\"versionEndExcluding\":\"6.6.66\",\"matchCriteriaId\":\"29A976AD-B9AB-4A95-9F08-7669F8847EB9\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"6.7\",\"versionEndExcluding\":\"6.12.5\",\"matchCriteriaId\":\"9501D045-7A94-42CA-8B03-821BE94A65B7\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:o:linux:linux_kernel:6.13:rc1:*:*:*:*:*:*\",\"matchCriteriaId\":\"62567B3C-6CEE-46D0-BC2E-B3717FBF7D13\"}]}]}],\"references\":[{\"url\":\"https://git.kernel.org/stable/c/0d6cd1151e26fc7c2d5daa85e8984aaa685a1a12\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/206d56f41a1509cadd06e2178c26cb830e45057d\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/456f08d24afa51b5eb816c42e4ca1c44a247bd42\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/5c9e3bb43a354a2245caebbbbb4a5b8c034fdd56\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/905d82e6e77d16ec3e089c92b7b59a14899dfc1a\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/ca70b8baf2bd125b2a4d96e76db79375c07d7ff2\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://git.kernel.org/stable/c/dbedc7e142df5ea238a46fdd7462c1c42cd36a10\",\"source\":\"416baaa9-dc9f-4396-8d5f-8c081fb06d67\",\"tags\":[\"Patch\"]},{\"url\":\"https://lists.debian.org/debian-lts-announce/2025/03/msg00001.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"}]}}"
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.