FKIE_CVE-2023-54246
Vulnerability from fkie_nvd - Published: 2025-12-30 13:16 - Updated: 2026-06-17 06:47
Severity
Summary
In the Linux kernel, the following vulnerability has been resolved:
rcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle()
The rcuscale.holdoff module parameter can be used to delay the start
of rcu_scale_writer() kthread. However, the hung-task timeout will
trigger when the timeout specified by rcuscale.holdoff is greater than
hung_task_timeout_secs:
runqemu kvm nographic slirp qemuparams="-smp 4 -m 2048M"
bootparams="rcuscale.shutdown=0 rcuscale.holdoff=300"
[ 247.071753] INFO: task rcu_scale_write:59 blocked for more than 122 seconds.
[ 247.072529] Not tainted 6.4.0-rc1-00134-gb9ed6de8d4ff #7
[ 247.073400] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[ 247.074331] task:rcu_scale_write state:D stack:30144 pid:59 ppid:2 flags:0x00004000
[ 247.075346] Call Trace:
[ 247.075660] <TASK>
[ 247.075965] __schedule+0x635/0x1280
[ 247.076448] ? __pfx___schedule+0x10/0x10
[ 247.076967] ? schedule_timeout+0x2dc/0x4d0
[ 247.077471] ? __pfx_lock_release+0x10/0x10
[ 247.078018] ? enqueue_timer+0xe2/0x220
[ 247.078522] schedule+0x84/0x120
[ 247.078957] schedule_timeout+0x2e1/0x4d0
[ 247.079447] ? __pfx_schedule_timeout+0x10/0x10
[ 247.080032] ? __pfx_rcu_scale_writer+0x10/0x10
[ 247.080591] ? __pfx_process_timeout+0x10/0x10
[ 247.081163] ? __pfx_sched_set_fifo_low+0x10/0x10
[ 247.081760] ? __pfx_rcu_scale_writer+0x10/0x10
[ 247.082287] rcu_scale_writer+0x6b1/0x7f0
[ 247.082773] ? mark_held_locks+0x29/0xa0
[ 247.083252] ? __pfx_rcu_scale_writer+0x10/0x10
[ 247.083865] ? __pfx_rcu_scale_writer+0x10/0x10
[ 247.084412] kthread+0x179/0x1c0
[ 247.084759] ? __pfx_kthread+0x10/0x10
[ 247.085098] ret_from_fork+0x2c/0x50
[ 247.085433] </TASK>
This commit therefore replaces schedule_timeout_uninterruptible() with
schedule_timeout_idle().
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"kernel/rcu/rcuscale.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "55887adc76e19aec9763186e2c1d0a3481d20e96",
"status": "affected",
"version": "df37e66bfdbb57e8cae7dbf39a0c66b1b8701338",
"versionType": "git"
},
{
"lessThan": "4f03fba096bfded90e0d71eba8839a46922164d1",
"status": "affected",
"version": "df37e66bfdbb57e8cae7dbf39a0c66b1b8701338",
"versionType": "git"
},
{
"lessThan": "83ed0cdb6ae0383dd14b02375c353773836884ed",
"status": "affected",
"version": "df37e66bfdbb57e8cae7dbf39a0c66b1b8701338",
"versionType": "git"
},
{
"lessThan": "9416dccb31fdb190d25d57e97674f232651f6560",
"status": "affected",
"version": "df37e66bfdbb57e8cae7dbf39a0c66b1b8701338",
"versionType": "git"
},
{
"lessThan": "e60c122a1614b4f65b29a7bef9d83b9fd30e937a",
"status": "affected",
"version": "df37e66bfdbb57e8cae7dbf39a0c66b1b8701338",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"kernel/rcu/rcuscale.c"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "4.7"
},
{
"lessThan": "4.7",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.10.*",
"status": "unaffected",
"version": "5.10.197",
"versionType": "semver"
},
{
"lessThanOrEqual": "5.15.*",
"status": "unaffected",
"version": "5.15.133",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.1.*",
"status": "unaffected",
"version": "6.1.55",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.5.*",
"status": "unaffected",
"version": "6.5.5",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "6.6",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "In the Linux kernel, the following vulnerability has been resolved:\n\nrcuscale: Move rcu_scale_writer() schedule_timeout_uninterruptible() to _idle()\n\nThe rcuscale.holdoff module parameter can be used to delay the start\nof rcu_scale_writer() kthread. However, the hung-task timeout will\ntrigger when the timeout specified by rcuscale.holdoff is greater than\nhung_task_timeout_secs:\n\nrunqemu kvm nographic slirp qemuparams=\"-smp 4 -m 2048M\"\nbootparams=\"rcuscale.shutdown=0 rcuscale.holdoff=300\"\n\n[ 247.071753] INFO: task rcu_scale_write:59 blocked for more than 122 seconds.\n[ 247.072529] Not tainted 6.4.0-rc1-00134-gb9ed6de8d4ff #7\n[ 247.073400] \"echo 0 \u003e /proc/sys/kernel/hung_task_timeout_secs\" disables this message.\n[ 247.074331] task:rcu_scale_write state:D stack:30144 pid:59 ppid:2 flags:0x00004000\n[ 247.075346] Call Trace:\n[ 247.075660] \u003cTASK\u003e\n[ 247.075965] __schedule+0x635/0x1280\n[ 247.076448] ? __pfx___schedule+0x10/0x10\n[ 247.076967] ? schedule_timeout+0x2dc/0x4d0\n[ 247.077471] ? __pfx_lock_release+0x10/0x10\n[ 247.078018] ? enqueue_timer+0xe2/0x220\n[ 247.078522] schedule+0x84/0x120\n[ 247.078957] schedule_timeout+0x2e1/0x4d0\n[ 247.079447] ? __pfx_schedule_timeout+0x10/0x10\n[ 247.080032] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.080591] ? __pfx_process_timeout+0x10/0x10\n[ 247.081163] ? __pfx_sched_set_fifo_low+0x10/0x10\n[ 247.081760] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.082287] rcu_scale_writer+0x6b1/0x7f0\n[ 247.082773] ? mark_held_locks+0x29/0xa0\n[ 247.083252] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.083865] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.084412] kthread+0x179/0x1c0\n[ 247.084759] ? __pfx_kthread+0x10/0x10\n[ 247.085098] ret_from_fork+0x2c/0x50\n[ 247.085433] \u003c/TASK\u003e\n\nThis commit therefore replaces schedule_timeout_uninterruptible() with\nschedule_timeout_idle()."
},
{
"lang": "es",
"value": "En el kernel de Linux, la siguiente vulnerabilidad ha sido resuelta:\n\nrcuscale: Mover rcu_scale_writer() schedule_timeout_uninterruptible() a _idle()\n\nEl par\u00e1metro del m\u00f3dulo rcuscale.holdoff puede ser usado para retrasar el inicio del kthread rcu_scale_writer(). Sin embargo, el tiempo de espera de tarea colgada se activar\u00e1 cuando el tiempo de espera especificado por rcuscale.holdoff sea mayor que hung_task_timeout_secs:\n\nrunqemu kvm nographic slirp qemuparams=\"-smp 4 -m 2048M\"\nbootparams=\"rcuscale.shutdown=0 rcuscale.holdoff=300\"\n\n[ 247.071753] INFO: tarea rcu_scale_write:59 bloqueada por m\u00e1s de 122 segundos.\n[ 247.072529] No contaminado 6.4.0-rc1-00134-gb9ed6de8d4ff #7\n[ 247.073400] \u0027echo 0 \u0026gt; /proc/sys/kernel/hung_task_timeout_secs\u0027 deshabilita este mensaje.\n[ 247.074331] tarea:rcu_scale_write estado:D pila:30144 pid:59 ppid:2 flags:0x00004000\n[ 247.075346] Rastreo de Llamada:\n[ 247.075660] \n[ 247.075965] __schedule+0x635/0x1280\n[ 247.076448] ? __pfx___schedule+0x10/0x10\n[ 247.076967] ? schedule_timeout+0x2dc/0x4d0\n[ 247.077471] ? __pfx_lock_release+0x10/0x10\n[ 247.078018] ? enqueue_timer+0xe2/0x220\n[ 247.078522] schedule+0x84/0x120\n[ 247.078957] schedule_timeout+0x2e1/0x4d0\n[ 247.079447] ? __pfx_schedule_timeout+0x10/0x10\n[ 247.080032] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.080591] ? __pfx_process_timeout+0x10/0x10\n[ 247.081163] ? __pfx_sched_set_fifo_low+0x10/0x10\n[ 247.081760] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.082287] rcu_scale_writer+0x6b1/0x7f0\n[ 247.082773] ? mark_held_locks+0x29/0xa0\n[ 247.083252] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.083865] ? __pfx_rcu_scale_writer+0x10/0x10\n[ 247.084412] kthread+0x179/0x1c0\n[ 247.084759] ? __pfx_kthread+0x10/0x10\n[ 247.085098] ret_from_fork+0x2c/0x50\n[ 247.085433] \n\nEste commit por lo tanto reemplaza schedule_timeout_uninterruptible() con schedule_timeout_idle()."
}
],
"id": "CVE-2023-54246",
"lastModified": "2026-06-17T06:47:05.173",
"metrics": {},
"published": "2025-12-30T13:16:13.210",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/4f03fba096bfded90e0d71eba8839a46922164d1"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/55887adc76e19aec9763186e2c1d0a3481d20e96"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/83ed0cdb6ae0383dd14b02375c353773836884ed"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/9416dccb31fdb190d25d57e97674f232651f6560"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/e60c122a1614b4f65b29a7bef9d83b9fd30e937a"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Deferred"
}
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.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
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
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
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.