affected products in the CVE record: Linux · LinuxCPE names NVD's analysts give as vulnerable: o:linux:linux_kernelthe product type of Linux kernel in nday's product registry
stage
DIS
disclosed
cvss
no score yet
# Lifecycle
x axis UTC; dot = exact minute, wide bar = date only, hollow = unknown or inferred.
time unknown
DISdisclosed
PATpatch
no record yet
ANAanalysis
no record yet
POCPoC
no record yet
ITWexploited
no record yet
KEVKEV
no record yet
# Summary
In the Linux kernel, the following vulnerability has been resolved:
cpufreq: schedutil: Use kobject release() method to free sugov_tunables
The struct sugov_tunables is protected by the kobject, so we can't free
it directly. Otherwise we would get a call trace like this:
ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x30WARNING: CPU: 3 PID: 720 at lib/debugobjects.c:505debug_print_object+0xb8/0x100Modules linked in:CPU: 3 PID: 720 Comm: a.sh Tainted: G W 5.14.0-rc1-next-20210715-yocto-standard+ #507
Hardware name: Marvell OcteonTX CN96XX board (DT)
pstate: 40400009 (nZcv daif +PAN -UAO -TCO BTYPE=--)
pc : debug_print_object+0xb8/0x100lr : debug_print_object+0xb8/0x100sp : ffff80001ecaf910x29: ffff80001ecaf910 x28: ffff00011b10b8d0 x27: ffff800011043d80x26: ffff00011a8f0000 x25: ffff800013cb3ff0 x24: 0000000000000000x23: ffff80001142aa68 x22: ffff800011043d80 x21: ffff00010de46f20x20: ffff800013c0c520 x19: ffff800011d8f5b0 x18: 0000000000000010x17: 6e6968207473696c x16: 5f72656d6974203a x15: 6570797420746365x14: 6a626f2029302065 x13: 303378302f307830 x12: 2b6e665f72656d69x11: ffff8000124b1560 x10: ffff800012331520 x9 : ffff8000100ca6b0x8 : 000000000017ffe8 x7 : c0000000fffeffff x6 : 0000000000000001x5 : ffff800011d8c000 x4 : ffff800011d8c740 x3 : 0000000000000000x2 : ffff0001108301c0 x1 : ab3c90eedf9c0f00 x0 : 0000000000000000Call trace:debug_print_object+0xb8/0x100__debug_check_no_obj_freed+0x1c0/0x230debug_check_no_obj_freed+0x20/0x88slab_free_freelist_hook+0x154/0x1c8kfree+0x114/0x5d0sugov_exit+0xbc/0xc0cpufreq_exit_governor+0x44/0x90cpufreq_set_policy+0x268/0x4a8store_scaling_governor+0xe0/0x128store+0xc0/0xf0sysfs_kf_write+0x54/0x80kernfs_fop_write_iter+0x128/0x1c0new_sync_write+0xf0/0x190vfs_write+0x2d4/0x478ksys_write+0x74/0x100__arm64_sys_write+0x24/0x30invoke_syscall.constprop.0+0x54/0xe0do_el0_svc+0x64/0x158el0_svc+0x2c/0xb0el0t_64_sync_handler+0xb0/0xb8el0t_64_sync+0x198/0x19cirq event stamp: 5518
hardirqs last enabled at (5517): [<ffff8000100cbd7c>]console_unlock+0x554/0x6c8hardirqs last disabled at (5518): [<ffff800010fc0638>]el1_dbg+0x28/0xa0softirqs last enabled at (5504): [<ffff8000100106e0>]__do_softirq+0x4d0/0x6c0softirqs last disabled at (5483): [<ffff800010049548>]irq_exit+0x1b0/0x1b8
So split the original sugov_tunables_free() into two functions,
sugov_clear_global_tunables() is just used to clear the global_tunables
and the new sugov_tunables_free() is used as kobj_type::release to
release the sugov_tunables safely.
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
# Keyboard shortcuts
j / k
next / previous row (list rows or events)
Enter
open the vulnerability under the cursor
/
search (Esc leaves the box)
y
copy the CVE ID
o
open the event's source (vulnerability page)
u
back
?
show / hide this help
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.show {n} moreview on XThe posts could not be loaded.nday has not collected any post on X by listed researchers that mentions this CVE.expandcollapsesending…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.