-
Notifications
You must be signed in to change notification settings - Fork 10
[lts92] Many VULNs 9-15-25 #575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
bmastbergen
merged 13 commits into
ciqlts9_2
from
bmastbergen_ciqlts9_2/many-vulns-9-15-25
Sep 18, 2025
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6840140
netfilter: nftables: exthdr: fix 4-byte stack OOB write
bmastbergen b97f8a6
net/ipv6: avoid possible UAF in ip6_route_mpath_notify()
bmastbergen b318494
net: fix out-of-bounds access in ops_init
bmastbergen 0a71514
tcp: Use refcount_inc_not_zero() in tcp_twsk_unique().
bmastbergen b1c7e8e
net: sched: sch_multiq: fix possible OOB write in multiq_tune()
bmastbergen 893c028
locks: fix KASAN: use-after-free in trace_event_raw_event_filelock_lock
bmastbergen 3f5ff6a
filelock: fix potential use-after-free in posix_lock_inode
bmastbergen 9db6d92
mptcp: pm: Fix uaf in __timer_delete_sync
bmastbergen f3e1356
padata: fix UAF in padata_reorder
bmastbergen 451a1cc
crypto: algif_hash - fix double free in hash_accept
bmastbergen cb97aff
wifi: rtw88: fix the 'para' buffer size to avoid reading out of bounds
bmastbergen e74a735
sch_hfsc: make hfsc_qlen_notify() idempotent
bmastbergen 36827f9
tipc: Fix use-after-free in tipc_conn_close().
bmastbergen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you pointed out on Slack, this leaves the
trace_posix_lock_inode()
call at the bottom of the function.I want to add though: leaving the
trace_posix_lock_inode()
outside of the spin lock is the cause of the CVE. So this not only results in a duplicate trace call, but also results in the CVE not getting fixed.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For posterity: this was an incorrect merge resolution by
git cherry-pick
because it does a 3-way merge, which is why this commit cherry-picked cleanly. Because to git, it looked like the deletion of the oldtrace_posix_lock_inode()
had already been done in this tree.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The previous commit is the
precoditional
fix which is pretty easy to see that it moved twice and without it we get a clean pick where this now has twotrace_psix_loc_indoe
calls. 893c028.While we don't have the exact example we can likely simulate it for internal and public facing docs in the GH wiki.