ksmbd: some potential bugfixes
Status from this message: Applied them to #ksmbd-for-next-next.
Get series with b4
b4 am 2026040644-brussels-dab-6f99@gregkhVersions newest first
Patches in v1 Applied
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | ksmbd: validate EaNameLength in smb2_get_ea()fs/ | +5 | 0 replies | |
| 2/3 | ksmbd: require 3 sub-authorities before reading sub_auth[2]fs/ | +2 | 0 replies | |
| 3/3 | ksmbd: fix mechToken leak when SPNEGO decode fails after token allocfs/ fs/ | +2 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] ksmbd: some potential bugfixes
I spent the time exercising some new fuzzing tools on the ksmbd and smb code purely because it's something that is simple to set up and test locally with virtual machines, and in doing so, potentially found some minor problems for when you have an "untrusted" client.
Here's some fixes for what I happened to notice. They pass my very limited testing here, but please don't trust them at all and verify that I'm not just making this all up before accepting them.
thanks!
greg k-h
Greg Kroah-Hartman (3):
ksmbd: validate EaNameLength in smb2_get_ea()
ksmbd: require 3 sub-authorities before reading sub_auth[2]
ksmbd: fix mechToken leak when SPNEGO decode fails after token alloc
fs/smb/server/connection.c | 1 + fs/smb/server/smb2pdu.c | 7 ++++++- fs/smb/server/smbacl.c | 3 ++- 3 files changed, 9 insertions(+), 2 deletions(-)
Signature · 1 line
2.53.0