ghsa-m43r-r9j3-6gfp
Vulnerability from github
Published
2025-03-27 18:31
Modified
2025-03-27 18:31
Details

In the Linux kernel, the following vulnerability has been resolved:

bpf: Skip task with pid=1 in send_signal_common()

The following kernel panic can be triggered when a task with pid=1 attaches a prog that attempts to send killing signal to itself, also see [1] for more details:

Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b CPU: 3 PID: 1 Comm: systemd Not tainted 6.1.0-09652-g59fe41b5255f #148 Call Trace: __dump_stack lib/dump_stack.c:88 [inline] dump_stack_lvl+0x100/0x178 lib/dump_stack.c:106 panic+0x2c4/0x60f kernel/panic.c:275 do_exit.cold+0x63/0xe4 kernel/exit.c:789 do_group_exit+0xd4/0x2a0 kernel/exit.c:950 get_signal+0x2460/0x2600 kernel/signal.c:2858 arch_do_signal_or_restart+0x78/0x5d0 arch/x86/kernel/signal.c:306 exit_to_user_mode_loop kernel/entry/common.c:168 [inline] exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203 __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline] syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296 do_syscall_64+0x44/0xb0 arch/x86/entry/common.c:86 entry_SYSCALL_64_after_hwframe+0x63/0xcd

So skip task with pid=1 in bpf_send_signal_common() to avoid the panic.

[1] https://lore.kernel.org/bpf/20221222043507.33037-1-sunhao.th@gmail.com

Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2023-52992"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-03-27T17:15:46Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\nbpf: Skip task with pid=1 in send_signal_common()\n\nThe following kernel panic can be triggered when a task with pid=1 attaches\na prog that attempts to send killing signal to itself, also see [1] for more\ndetails:\n\n  Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b\n  CPU: 3 PID: 1 Comm: systemd Not tainted 6.1.0-09652-g59fe41b5255f #148\n  Call Trace:\n  \u003cTASK\u003e\n  __dump_stack lib/dump_stack.c:88 [inline]\n  dump_stack_lvl+0x100/0x178 lib/dump_stack.c:106\n  panic+0x2c4/0x60f kernel/panic.c:275\n  do_exit.cold+0x63/0xe4 kernel/exit.c:789\n  do_group_exit+0xd4/0x2a0 kernel/exit.c:950\n  get_signal+0x2460/0x2600 kernel/signal.c:2858\n  arch_do_signal_or_restart+0x78/0x5d0 arch/x86/kernel/signal.c:306\n  exit_to_user_mode_loop kernel/entry/common.c:168 [inline]\n  exit_to_user_mode_prepare+0x15f/0x250 kernel/entry/common.c:203\n  __syscall_exit_to_user_mode_work kernel/entry/common.c:285 [inline]\n  syscall_exit_to_user_mode+0x1d/0x50 kernel/entry/common.c:296\n  do_syscall_64+0x44/0xb0 arch/x86/entry/common.c:86\n  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n\nSo skip task with pid=1 in bpf_send_signal_common() to avoid the panic.\n\n  [1] https://lore.kernel.org/bpf/20221222043507.33037-1-sunhao.th@gmail.com",
  "id": "GHSA-m43r-r9j3-6gfp",
  "modified": "2025-03-27T18:31:26Z",
  "published": "2025-03-27T18:31:26Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-52992"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0dfef503133565fa0bcf3268d8eeb5b181191a65"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1283a01b6e19d05f7ed49584ea653947245cd41e"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/4923160393b06a34759a11b17930d71e06f396f2"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a1c0263f1eb4deee132e11e52ee6982435460d81"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/a3d81bc1eaef48e34dd0b9b48eefed9e02a06451"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…