QID 198524

The io_uring subsystem in the linux kernel could be coerced to free adjacent memory.
The bpf subsystem in the linux kernel did not properly protect against speculative store bypass (ssb) side- channel attacks in some situations.
The bpf subsystem in the linux kernel did not properly protect against speculative store bypass (ssb) side-channel attacks in some situations.
The joystick device interface in the linux kernel did not properly validate data passed via an ioctl().the tracing subsystem in the linux kernel did not properly keep track of per-cpu ring buffer state.
The option usb high speed mobile device driver in the linux kernel did not properly handle error conditions.
The overlay file system in the linux kernel did not restrict private clones in some situations.
The virtio console implementation in the linux kernel did not properly validate input lengths in some situations.
The bpf subsystem in the linux kernel contained an integer overflow in its hash table implementation.
The nfsv4 client implementation in the linux kernel did not properly order connection setup operations.
The sun rpc implementation in the linux kernel contained an out-of-bounds access error.
The nfs server implementation in the linux kernel contained an out-of-bounds read when the trace even framework is being used for nfsd.
The btrfs file system in the linux kernel contained a race condition in situations that triggered allocations of new system chunks.
The max-3421 host usb device driver in the linux kernel did not properly handle device removal events.
The xilinx 10/100 ethernet lite device driver in the linux kernel could report pointer addresses in some situations.
The ext4 file system in the linux kernel contained a race condition when writing xattrs to an inode.

Note: The preceding description block is extracted directly from the security advisory. Using automation, we have attempted to clean and format it as much as possible without introducing additional issues.

a local attacker could use this to execute arbitrary code. (
Cve-2021-41073).
A local attacker could possibly use this to expose sensitive information. (
Cve-2021-34556).
A local attacker could possibly use this to expose sensitive information. (
Cve-2021-35477).
A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code on systems with a joystick device registered. (
Cve-2021-3612).
A privileged attacker could use this to cause a denial of service. (
Cve-2021-3679).
A physically proximate attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (
Cve-2021-37159).
An attacker could use this to expose sensitive information. (
Cve-2021-3732).
A local attacker could possibly use this to cause a denial of service (system crash) (cve-2021-38160).
A local attacker could use this to cause a denial of service (system crash) or possibly execute arbitrary code. (
Cve-2021-38166).
An attacker controlling a remote nfs server could use this to cause a denial of service on the client. (
Cve-2021-38199).
A remote attacker could possibly use this to cause a denial of service (system crash) (cve-2021-38201).
A remote attacker could possibly use this to cause a denial of service (system crash) (cve-2021-38202).
A local attacker could possibly use this to cause a denial of service (deadlock) (cve-2021-38203).
A physically proximate attacker could use this to cause a denial of service (system crash) (cve-2021-38204).
An attacker could use this information to ease the exploitation of another vulnerability. (
Cve-2021-38205).
A local attacker could use this to cause a denial of service or possibly gain administrative privileges. (
Cve-2021-40490).