affected products in the CVE record: Linux · Linuxthe product type of Linux kernel in nday's product registry
현재 단계
DIS
공개
CVSS
점수 없음
# 생명주기
가로축 UTC. 점 = 분 단위, 넓은 막대 = 날짜만, 빈 표시 = 불명 또는 추정.
시점 알 수 없음
DIS공개
PAT패치
아직 기록 없음
ANA분석
아직 기록 없음
POCPoC
아직 기록 없음
ITW악용
아직 기록 없음
KEVKEV
아직 기록 없음
# 요약
In the Linux kernel, the following vulnerability has been resolved:
cgroup/cpuset: Handle cpu hotplug race in guarantee_active_cpus()
With commit 2125c0034c5d ("cgroup/cpuset: Make cpuset hotplug processing
synchronous"), the cpuset hotplug operation becomes synchronous. That
commit also removes the code that handles race between cpuset_hotplug_work
and cpu hotplug notifier with the assumption that race is now gone.
Later commit 7a0aabd9ce69 ("cgroup/cpuset: Always use cpu_active_mask")
updates the cpuset code to always use cpu_active_mask instead of
cpu_online_mask in some places including guarantee_online_cpus() which
is renamed to guarantee_active_cpus() in that commit.
In the case of CPU offline operation, cpu_active_mask is updated
first in sched_cpu_deactivate() to remove the offline CPU before
cpuset_handle_hotplug() is called to update the effective_cpus of the
affected cpusets. The cpu_online_mask is updated after that near the end
of the offline operation to remove the offline CPU. As a result, the race
comes back and the top cpuset may not have any active CPU leading to NULL
pointer dereference during the race window when guarantee_active_cpus()
is called after cpu_active_mask is updated to remove the CPU to be torn
down but before cpuset_handle_hotplug() is able to properly update the
effective_cpus of the top cpuset.
Fix this by adding back the NULL cs check to avoid this problem.
Original text of the CVE record (cvelist), shown as published.
Your account is suspended: you cannot comment, reply, edit or report. You can still delete your own comments.
formatting
↵↵
empty line: new paragraph
↵
line break: kept as is
*…*
emphasis
**…**
bold
`…`
inline code
```
on its own line: starts and ends a code block
> …
quote
- …
list
1. …
numbered list
[…](https://…)
link (http and https only)
https://…
bare address: link
CVE-2026-1234
links to that vulnerability on nday
\*
shows the character itself
Headings, images, tables, nested lists and HTML are shown as plain text.
Links from new accounts are shown as plain text; CVE IDs are always linked.
reported
# 키보드 단축키
j / k
다음/이전 행(목록 행 또는 이벤트)
Enter
커서가 있는 취약점 열기
/
검색(Esc 키로 검색창 나가기)
y
CVE ID 복사
o
이벤트 출처 열기(취약점 페이지)
u
뒤로
?
이 도움말 표시/숨기기
sign inaccountmodadminAdminProfileFollowingSecurityDeveloperSign outSigned in.Sign-in method linked to your account.Sign-in was cancelled at the provider; nothing changed.That login already belongs to another nday account, or this account already has one from the same provider. Nothing was linked.Sign-in did not complete. Try again.You are still signed in as before: that login belongs to another nday account, or to none yet. Sign out first to use it.Linking was not completed because your last sign-in is no longer recent. Confirm it's you on the account page, then link again.This account is suspended, so new sign-in methods cannot be linked.Dismissworking…Delete this comment? This cannot be undone.Hidden by a moderator: {reason}text (moderators only)earlier versions: {n}replaced at {time}Posting needs the community rules accepted (version {version}).The community rules changed (version {version}); read and accept them to continue.Reported. A moderator will look at it.You have already reported this comment.You are signed out. Sign in again to continue.The request was refused as cross-site. Reload the page and try again.The session token changed. Reload the page and try again.Your account is suspended.Choose a handle on your account page first.Accept the current community rules first.Only moderators can do this.Only the author can do this.You cannot report your own comment.This comment changed in the meantime. Reload the page to see it as it is now.This comment or vulnerability does not exist (any more).Not a valid CVE ID.Only a visible top-level comment can get replies.This thread has reached its reply limit.You posted the same text here a moment ago.A comment needs 1 to {max} characters.Comments cannot be posted from this site language.Unknown purpose, or a purpose on a reply. Reload the page and try again.The reason is missing or too long.The note is too long.Unknown resolution.This position in the list is no longer valid. Reload the page.The request was malformed. Reload the page and try again.The text is too large.Too many requests. Try again in {seconds} s.Too many requests. Try again later.Daily limit reached. Try again after {time}.The server is busy. Try again in a moment.This address does not take comments. Open the page on the main site.Server error. Try again later.Network error: nday could not be reached. Check the connection and try again.The community rules changed while you were reading. Read them again.Write something first.Too long: {n} characters, at most {max}.Tick the box to accept the community rules first.Something went wrong ({code}). Try again.No comments yet.The discussion could not be loaded right now.more commentsfirst commentsmore repliesreplies[deleted account]link to this commenteditedposted on the {language} siteHidden by a moderator.Deleted by its author.technical analysisreproduction reportfix reportdetection methodquestionPlease include the affected version, the environment (OS, configuration), what you did and what happened, and your source.Please include the fixed version or patch, the environment, how you checked the fix and what happened, and your source.{n}건 더 보기X에서 보기게시물을 불러오지 못했습니다.명단의 연구자가 X에서 이 CVE를 언급한 게시물은 아직 수집되지 않았습니다.펼치기접기sending…Sent. An editor will look at it; you can follow its status here.titlesummaryaffected products or versionsfix informationtimeline eventsource linksotherwaiting for an editoracceptednot acceptedsent {at}Editors' note: {note}Sign in first.Your account is suspended.Choose a public handle on your account page first.Accept the current community rules on your account page first.The page's session expired; try again.The request was refused; reload the page and try again.Choose what is wrong.Write what is wrong, within the length limit.The evidence link must be a full http:// or https:// address.You already have several reports on this vulnerability waiting for an editor; wait until they are handled.This vulnerability already has many reports waiting for an editor; try again later.You reached the limit of reports for 24 hours; try again later.Too many requests; wait a moment and try again.This vulnerability was not found.The report is too large.Network error; try again.Write what is wrong first.Too long: at most {max} characters.Something went wrong; try again later.