GHSA-857X-V7JH-W473

Vulnerability from github – Published: 2025-12-24 15:30 – Updated: 2025-12-24 15:30
VLAI
Details

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

audit: fix possible soft lockup in __audit_inode_child()

Tracefs or debugfs maybe cause hundreds to thousands of PATH records, too many PATH records maybe cause soft lockup.

For example: 1. CONFIG_KASAN=y && CONFIG_PREEMPTION=n 2. auditctl -a exit,always -S open -k key 3. sysctl -w kernel.watchdog_thresh=5 4. mkdir /sys/kernel/debug/tracing/instances/test

There may be a soft lockup as follows: watchdog: BUG: soft lockup - CPU#45 stuck for 7s! [mkdir:15498] Kernel panic - not syncing: softlockup: hung tasks Call trace: dump_backtrace+0x0/0x30c show_stack+0x20/0x30 dump_stack+0x11c/0x174 panic+0x27c/0x494 watchdog_timer_fn+0x2bc/0x390 __run_hrtimer+0x148/0x4fc __hrtimer_run_queues+0x154/0x210 hrtimer_interrupt+0x2c4/0x760 arch_timer_handler_phys+0x48/0x60 handle_percpu_devid_irq+0xe0/0x340 __handle_domain_irq+0xbc/0x130 gic_handle_irq+0x78/0x460 el1_irq+0xb8/0x140 __audit_inode_child+0x240/0x7bc tracefs_create_file+0x1b8/0x2a0 trace_create_file+0x18/0x50 event_create_dir+0x204/0x30c __trace_add_new_event+0xac/0x100 event_trace_add_tracer+0xa0/0x130 trace_array_create_dir+0x60/0x140 trace_array_create+0x1e0/0x370 instance_mkdir+0x90/0xd0 tracefs_syscall_mkdir+0x68/0xa0 vfs_mkdir+0x21c/0x34c do_mkdirat+0x1b4/0x1d4 __arm64_sys_mkdirat+0x4c/0x60 el0_svc_common.constprop.0+0xa8/0x240 do_el0_svc+0x8c/0xc0 el0_svc+0x20/0x30 el0_sync_handler+0xb0/0xb4 el0_sync+0x160/0x180

Therefore, we add cond_resched() to __audit_inode_child() to fix it.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-54045"
  ],
  "database_specific": {
    "cwe_ids": [],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-24T13:16:06Z",
    "severity": null
  },
  "details": "In the Linux kernel, the following vulnerability has been resolved:\n\naudit: fix possible soft lockup in __audit_inode_child()\n\nTracefs or debugfs maybe cause hundreds to thousands of PATH records,\ntoo many PATH records maybe cause soft lockup.\n\nFor example:\n  1. CONFIG_KASAN=y \u0026\u0026 CONFIG_PREEMPTION=n\n  2. auditctl -a exit,always -S open -k key\n  3. sysctl -w kernel.watchdog_thresh=5\n  4. mkdir /sys/kernel/debug/tracing/instances/test\n\nThere may be a soft lockup as follows:\n  watchdog: BUG: soft lockup - CPU#45 stuck for 7s! [mkdir:15498]\n  Kernel panic - not syncing: softlockup: hung tasks\n  Call trace:\n   dump_backtrace+0x0/0x30c\n   show_stack+0x20/0x30\n   dump_stack+0x11c/0x174\n   panic+0x27c/0x494\n   watchdog_timer_fn+0x2bc/0x390\n   __run_hrtimer+0x148/0x4fc\n   __hrtimer_run_queues+0x154/0x210\n   hrtimer_interrupt+0x2c4/0x760\n   arch_timer_handler_phys+0x48/0x60\n   handle_percpu_devid_irq+0xe0/0x340\n   __handle_domain_irq+0xbc/0x130\n   gic_handle_irq+0x78/0x460\n   el1_irq+0xb8/0x140\n   __audit_inode_child+0x240/0x7bc\n   tracefs_create_file+0x1b8/0x2a0\n   trace_create_file+0x18/0x50\n   event_create_dir+0x204/0x30c\n   __trace_add_new_event+0xac/0x100\n   event_trace_add_tracer+0xa0/0x130\n   trace_array_create_dir+0x60/0x140\n   trace_array_create+0x1e0/0x370\n   instance_mkdir+0x90/0xd0\n   tracefs_syscall_mkdir+0x68/0xa0\n   vfs_mkdir+0x21c/0x34c\n   do_mkdirat+0x1b4/0x1d4\n   __arm64_sys_mkdirat+0x4c/0x60\n   el0_svc_common.constprop.0+0xa8/0x240\n   do_el0_svc+0x8c/0xc0\n   el0_svc+0x20/0x30\n   el0_sync_handler+0xb0/0xb4\n   el0_sync+0x160/0x180\n\nTherefore, we add cond_resched() to __audit_inode_child() to fix it.",
  "id": "GHSA-857x-v7jh-w473",
  "modified": "2025-12-24T15:30:36Z",
  "published": "2025-12-24T15:30:35Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-54045"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/0152e7758cc4e9f8bfba8dbea4438d8e488d6c08"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/1640c7bd4eddec6c72f3a99cbb74e333a2ce9f5d"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8a40b491372966ba5426e138a53460985565d5a6"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/8e76b944a7b9bddef190ffe2e29c9ae342ab91ed"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/98ef243d5900d75a64539a2165745bffbb155d43"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/9ca08adb75fb40a8f742c371927ee73f9dc753bf"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/b59bc6e37237e37eadf50cd5de369e913f524463"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/d061e2bfc20f2914656385816e0d20566213c54c"
    },
    {
      "type": "WEB",
      "url": "https://git.kernel.org/stable/c/f6364fa751d7486502c777f124a14d4d543fc5eb"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.