huzaifas-sidhpurwala/security-commit huggingface dataset:
CVE-2021-47338: kernel: fbmem: Do not delete the mode that is still in use
Component: kernel
Severity: Moderate
CWE: CWE-416 (Use After Free)
CVSS v3: 5.1 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's fbmem subsystem. This issue arises when the system attempts to delete a video mode that is still in use, leading to potential use-after-free errors. This improper handling can result in system crashes or undefined behavior when accessing freed memory.

Statement: This vulnerability is rated as a moderate severity because this issue affects system reliability by potentially causing errors when video modes are incorrectly managed, but it does not compromise the system's overall security posture or data integrity.

Affected upstream versions: 5.3
Fixed upstream versions: 0, 5.10.52, 5.12.19, 5.13.4, 5.14, 5.4.134
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 359311b85ebec7c07c3a08ae2f3def946cad33fa
CVE-2021-47352: kernel: virtio-net: Add validation for used length
Component: kernel
Severity: Moderate
CWE: CWE-20 (Improper Input Validation)
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel’s virtio-net driver, where the system does not properly validate the length of data provided by an untrusted device. This lack of validation could lead to data corruption if the length of the data is incorrect or maliciously crafted.

Statement: This vulnerability is rated as a moderate severity because it involves potential data corruption or loss, but requires exploitation through specific conditions involving untrusted devices and does not directly impact system confidentiality or integrity, but can lead to significant system disruptions.

Affected upstream versions: 4.11
Fixed upstream versions: 0, 5.10.51, 5.12.18, 5.13.3, 5.14, 5.4.293
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: c1b40d1959517ff2ea473d40eeab4691d6d62462
CVE-2021-47353: kernel: udf: Fix NULL pointer dereference in udf_symlink function
Component: kernel
Severity: Moderate
CWE: CWE-476 (NULL Pointer Dereference)
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's UDF file system driver, where the udf_symlink function can dereference a NULL pointer. This occurs because the function uses a value returned from udf_tgetblk without checking if it is NULL, potentially causing system crashes if sb_getblk fails.

Statement: This vulnerability is rated as a moderate severity because it can lead to system crashes due to a NULL pointer dereference, but it requires specific conditions related to file system operations.

Affected upstream versions: 2.6.12
Fixed upstream versions: 0, 4.14.240, 4.19.198, 4.4.276, 4.9.276, 5.10.51, 5.12.18, 5.13.3, 5.14, 5.4.133
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 2f3d9ddd32a28803baa547e6274983b67d5e287c
CVE-2021-47356: kernel: mISDN: fix possible use-after-free in HFC_cleanup()
Component: kernel
Severity: Moderate
CWE: CWE-416 (Use After Free)
CVSS v3: 6.7 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's mISDN driver. This issue arises during the cleanup process, where a timer handler might still be running after the driver has been removed, which can lead to a use-after-free issue, potentially causing a system crash.

Statement: This vulnerability is rated as a moderate severity because it can cause system crash but it requires a specific conditions to be triggered, including the concurrent removal of the driver and active timer operations.

Affected upstream versions: 2.6.29
Fixed upstream versions: 0, 4.14.240, 4.19.198, 4.4.276, 4.9.276, 5.10.51, 5.12.18, 5.13.3, 5.14, 5.4.133
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 49331c07ef0f8fdfa42b30ba6a83a657b29d7fbe
CVE-2021-47373: kernel: irqchip/gic-v3-its: Fix potential VPE leak on error
Component: kernel
Severity: Low
CWE: CWE-402 (Transmission of Private Resources into a New Sphere ('Resource Leak'))
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N)
Public date: 2024-05-21T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

irqchip/gic-v3-its: Fix potential VPE leak on error

In its_vpe_irq_domain_alloc, when its_vpe_init() returns an error,
there is an off-by-one in the number of VPEs to be freed.

Fix it by simply passing the number of VPEs allocated, which is the
index of the loop iterating over the VPEs.

[maz: fixed commit message]


Affected upstream versions: 4.14
Fixed upstream versions: 0, 4.14.249, 4.19.209, 5.10.70, 5.14.9, 5.15, 5.4.150
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 7d39992d45acd6f2d6b2f62389c55b61fb3d486b
CVE-2021-47378: kernel: nvme-rdma: destroy cm id before destroy qp to avoid use after free
Component: kernel
Severity: Moderate
CWE: CWE-416 (Use After Free)
CVSS v3: 6 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's nvme-rdma driver where the driver failed to destroy a component cm_id before another component qp was destroyed. This issue occurs when the kernel incorrectly manages memory during RDMA, leading to a potential use-after-free.

Statement: This vulnerability is rated as a Moderate severity. Although it can lead to system crashes due to improper memory access, it does not directly compromise data security or integrity.

This bug only affects Red Hat Enterprise Linux 9.0. A fix was commited to Red Hat Enterprise Linux 9.1, which is why the bug does not affect Red Hat Enterprise Linux 9.2 and later.

Affected upstream versions: 4.8
Fixed upstream versions: 0, 5.10.70, 5.14.9, 5.15
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: ecf0dc5a904830c926a64feffd8e01141f89822f
CVE-2021-47383: kernel: tty: Fix out-of-bound vmalloc access in imageblit
Component: kernel
Severity: Moderate
CWE: CWE-125 (Out-of-bounds Read)
CVSS v3: 6.6 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's tty subsystem within the imageblit function when a userspace program performs an ioctl operation with the FBIOPUT_VSCREENINFO command, passing a fb_var_screeninfo structure with limited fields. If the structure’s values remain unchanged from a previous ioctl call, the kernel fails to fully update the screen information, leading to incorrect calculations of screen dimensions potentially causing system crashes or instability.

Statement: This vulnerability is rated as a moderate severity because it can lead to system crashes by accessing invalid memory addresses, it does not pose a direct threat to data security or allow unauthorized access.

Affected upstream versions: 2.6.12
Fixed upstream versions: 0, 4.14.249, 4.19.209, 4.4.286, 4.9.285, 5.10.71, 5.14.10, 5.15, 5.4.151
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 7e71fcedfda6f7de18f850a6b36e78d78b04476f
CVE-2021-47384: kernel: hwmon: (w83793) Fix NULL pointer dereference by removing unnecessary structure field
Component: kernel
Severity: Moderate
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's hwmon driver for the w83793 module where NULL pointer dereference caused by an obsolete structure field lm75[]. During specific device read operations, if certain values are read from the device, the driver could attempt to access a NULL pointer, leading to potential system crashes or instability.

Statement: This vulnerability is rated as a moderate severity because the impact is limited to system stability rather than unauthorized access or data exposure.

Affected upstream versions: 5.4
Fixed upstream versions: 0, 5.10.71, 5.14.10, 5.15, 5.4.151
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 6cb01fe630eaffc5a2c3f7364436caddba286623
CVE-2021-47385: kernel: hwmon: (w83792d) Fix NULL pointer dereference by removing unnecessary structure field
Component: kernel
Severity: Moderate
CWE: CWE-476 (NULL Pointer Dereference)
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's hwmon driver for the w83792d module where a NULL pointer dereference was caused by the  lm75[] obsolete structure field. During specific device read operations, if certain conditions are met, the driver may attempt to access a NULL pointer because this unnecessary field is being retained, which can lead to system crashes or instability.

Statement: This vulnerability is rated as a Moderate severity because it can cause crashes and operational disruptions. It does not expose sensitive information or allow unauthorized access.

Affected upstream versions: 5.4
Fixed upstream versions: 0, 5.10.71, 5.14.10, 5.15, 5.4.151
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 200ced5ba724d8bbf29dfac4ed1e17a39ccaccd1
CVE-2021-47386: kernel: hwmon: (w83791d) Fix NULL pointer dereference by removing unnecessary structure field
Component: kernel
Severity: Moderate
CWE: CWE-476 (NULL Pointer Dereference)
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's hwmon driver in the w83791d module where the driver performs a read operation, which can result in a NULL pointer dereference. This occurs due to an unnecessary field (lm75[]) that is no longer needed after updates to device handling functions, the driver could attempt to access a NULL pointer, leading to potential system crashes.

Statement: This vulnerability is rated as a moderate severity because the risk is linked to system crashes or unexpected behavior, which can disrupt normal operations but does not directly compromise sensitive data or allow unauthorized access.

Affected upstream versions: 5.4
Fixed upstream versions: 0, 5.10.71, 5.14.10, 5.15, 5.4.151
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 44d3c480e4e2a75bf6296a18b4356157991ccd80
CVE-2021-47393: kernel: hwmon: (mlxreg-fan) Return non-zero value when fan current state is enforced from sysfs
Component: kernel
Severity: Moderate
CWE: CWE-754 (Improper Check for Unusual or Exceptional Conditions)
CVSS v3: 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel's hwmon subsystem, specifically in the mlxreg-fan driver. The issue arises when the driver’s sysfs interface for controlling fan speed does not properly handle cases where the requested minimum fan speed exceeds the maximum allowable value. When the value provided is out of bounds, it results in a non-zero return code that prevents updates to thermal statistics, which can lead to a slab-out-of-bounds error, potentially causing system instability or crashes due to improper access to memory.

Statement: This vulnerability is rated as a moderate severity because it can disrupt system operation by causing crashes or unpredictable behaviour under specific conditions.

Affected upstream versions: 4.19
Fixed upstream versions: 0, 4.19.209, 5.10.71, 5.14.10, 5.15, 5.4.151
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 5c6e0bce647d9cb32a17d58ffa669b3421fcc6ca
CVE-2021-47400: kernel: net: hns3: do not allow call hns3_nic_net_open repeatedly
Component: kernel
Severity: Moderate
CWE: CWE-664 (Improper Control of a Resource Through its Lifetime)
CVSS v3: 4.1 (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was discovered in the Linux kernel's hns3 network driver. The hns3_nic_net_open() function is designed to be called only once per device instance. However, due to insufficient checks, multiple calls to this function are possible. This can lead to scenarios where hns3_nic_net_open() is invoked concurrently, potentially causing system crashes.

Statement: This vulnerability is rated as moderate because its impact is limited by specific conditions that need to be met for exploitation.

Affected upstream versions: 5.0
Fixed upstream versions: 0, 5.10.71, 5.14.10, 5.15, 5.4.151
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 5a31d4e73ada8022427b69b10fd1f01a6a8d4b3d
CVE-2021-47408: kernel: netfilter: conntrack: serialize hash resizes and cleanups
Component: kernel
Severity: Moderate
CWE: CWE-667 (Improper Locking)
CVSS v3: 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel’s netfilter and conntrack module, occurring during the resizing and cleanup of hash tables used for connection tracking. The kernel's nf_ct_iterate_cleanup() function fails to efficiently handle simultaneous hash resizes and cleanups, leading to prolonged delays lead to unresponsive system behavior.

Statement: This vulnerability is rated as a moderate severity because it impacts on system availability rather than data security, affects system performance and responsiveness, particularly during cleanup operations under high load conditions

Affected upstream versions: 4.13
Fixed upstream versions: 0, 5.10.71, 5.14.10, 5.15
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: e2d192301a0df8160d1555b66ae8611e8050e424
CVE-2021-47412: kernel: block: don't call rq_qos_ops->done_bio if the bio isn't tracked
Component: kernel
Severity: Moderate
CWE: CWE-364 (Signal Handler Race Condition)
CVSS v3: 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

A vulnerability was found in the Linux kernel, where improper handling of block I/O requests when a block I/O request (bio) is not tracked, the kernel erroneously calls the rq_qos_ops->done_bio function, potentially leading to use-after-free issues. This situation can occurr when the request queue is accessed after it has been freed, resulting in possible kernel panic.

Statement: This vulnerability is classified as moderate severity, as the issue can cause kernel panics, leading to system crashes. However, it does not affect data confidentiality or integrity.

Affected upstream versions: 4.19
Fixed upstream versions: 0, 5.10.241, 5.14.11, 5.15
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: db60edbfff332a6a5477c367af8125f034570989
CVE-2021-47429: kernel: powerpc/64s: Fix unrecoverable MCE calling async handler from NMI
Component: kernel
Severity: Low
CWE: CWE-99 (Improper Control of Resource Identifiers ('Resource Injection'))
CVSS v3: 4.4 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

powerpc/64s: Fix unrecoverable MCE calling async handler from NMI

The machine check handler is not considered NMI on 64s. The early
handler is the true NMI handler, and then it schedules the
machine_check_exception handler to run when interrupts are enabled.

This works fine except the case of an unrecoverable MCE, where the true
NMI is taken when MSR[RI] is clear, it can not recover, so it calls
machine_check_exception directly so something might be done about it.

Calling an async handler from NMI context can result in irq state and
other things getting corrupted. This can also trigger the BUG at
  arch/powerpc/include/asm/interrupt.h:168
  BUG_ON(!arch_irq_disabled_regs(regs) && !(regs->msr & MSR_EE));

Fix this by making an _async version of the handler which is called
in the normal case, and a NMI version that is called for unrecoverable
interrupts.


Affected upstream versions: 5.14
Fixed upstream versions: 0, 5.14.12, 5.15
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: d7a8e38999fbd6910516e44cb43f9f4317e54f73
CVE-2021-47432: kernel: lib/generic-radix-tree.c: Don't overflow in peek()
Component: kernel
Severity: Low
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-21T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

lib/generic-radix-tree.c: Don't overflow in peek()

When we started spreading new inode numbers throughout most of the 64
bit inode space, that triggered some corner case bugs, in particular
some integer overflows related to the radix tree code. Oops.


Affected upstream versions: 5.1
Fixed upstream versions: 0, 6.1.64, 6.5.13, 6.6.3, 6.7
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 784d01f9bbc282abb0c5ade5beb98a87f50343ac
CVE-2021-47454: kernel: powerpc/smp: do not decrement idle task preempt count in CPU offline
Component: kernel
Severity: Moderate
CWE: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))
CVSS v3: 4.1 (CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-22T00:00:00+00:00

A vulnerability was found in the Linux kernel's powerpc/smp architecture, where the idle task's preemption count was incorrectly decremented during the CPU offline process. This issue caused a "scheduling while atomic" error when a CPU was offlined and then onlined again, leading to potential system instability.


Affected upstream versions: 5.10.50 < 5.10.76, 5.12.17 < 5.13, 5.13.2 < 5.14, 5.14
Fixed upstream versions: 0, 5.10.76, 5.13, 5.14, 5.14.15, 5.15
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 53770a411559cf7bc0906d1df319cc533d2f4f58
CVE-2021-47455: kernel: ptp: Fix possible memory leak in ptp_clock_register()
Component: kernel
Severity: Low
CVSS v3: 5.1 (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:L)
Public date: 2024-05-22T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

ptp: Fix possible memory leak in ptp_clock_register()

I got memory leak as follows when doing fault injection test:

unreferenced object 0xffff88800906c618 (size 8):
  comm "i2c-idt82p33931", pid 4421, jiffies 4294948083 (age 13.188s)
  hex dump (first 8 bytes):
    70 74 70 30 00 00 00 00                          ptp0....
  backtrace:
    [<00000000312ed458>] __kmalloc_track_caller+0x19f/0x3a0
    [<0000000079f6e2ff>] kvasprintf+0xb5/0x150
    [<0000000026aae54f>] kvasprintf_const+0x60/0x190
    [<00000000f323a5f7>] kobject_set_name_vargs+0x56/0x150
    [<000000004e35abdd>] dev_set_name+0xc0/0x100
    [<00000000f20cfe25>] ptp_clock_register+0x9f4/0xd30 [ptp]
    [<000000008bb9f0de>] idt82p33_probe.cold+0x8b6/0x1561 [ptp_idt82p33]

When posix_clock_register() returns an error, the name allocated
in dev_set_name() will be leaked, the put_device() should be used
to give up the device reference, then the name will be freed in
kobject_cleanup() and other memory will be freed in ptp_clock_release().


Affected upstream versions: 3.16.83 < 3.17, 4.4.224 < 4.5, 4.9.224 < 4.10, 4.14.162 < 4.15, 4.19.93 < 4.20, 5.4.8 < 5.5, 5.5
Fixed upstream versions: 0, 3.17, 4.10, 4.15, 4.20, 4.5, 5.10.241, 5.14.15, 5.15, 5.5
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: f1c96d8085588e1b997a96214b409ac3be20b524
CVE-2021-47456: kernel: can: peak_pci: peak_pci_remove(): fix UAF
Component: kernel
Severity: Low
CWE: CWE-416 (Use After Free)
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-22T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

can: peak_pci: peak_pci_remove(): fix UAF

When remove the module peek_pci, referencing 'chan' again after
releasing 'dev' will cause UAF.

Fix this by releasing 'dev' later.

The following log reveals it:

[   35.961814 ] BUG: KASAN: use-after-free in peak_pci_remove+0x16f/0x270 [peak_pci]
[   35.963414 ] Read of size 8 at addr ffff888136998ee8 by task modprobe/5537
[   35.965513 ] Call Trace:
[   35.965718 ]  dump_stack_lvl+0xa8/0xd1
[   35.966028 ]  print_address_description+0x87/0x3b0
[   35.966420 ]  kasan_report+0x172/0x1c0
[   35.966725 ]  ? peak_pci_remove+0x16f/0x270 [peak_pci]
[   35.967137 ]  ? trace_irq_enable_rcuidle+0x10/0x170
[   35.967529 ]  ? peak_pci_remove+0x16f/0x270 [peak_pci]
[   35.967945 ]  __asan_report_load8_noabort+0x14/0x20
[   35.968346 ]  peak_pci_remove+0x16f/0x270 [peak_pci]
[   35.968752 ]  pci_device_remove+0xa9/0x250


Affected upstream versions: 3.4
Fixed upstream versions: 0, 4.14.253, 4.19.214, 4.4.290, 4.9.288, 5.10.76, 5.14.15, 5.15, 5.4.156
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 1c616528ba4aeb1125a06b407572ab7b56acae38
CVE-2021-47457: kernel: can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible()
Component: kernel
Severity: Low
CWE: CWE-99 (Improper Control of Resource Identifiers ('Resource Injection'))
CVSS v3: 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H)
Public date: 2024-05-22T00:00:00+00:00

In the Linux kernel, the following vulnerability has been resolved:

can: isotp: isotp_sendmsg(): add result check for wait_event_interruptible()

Using wait_event_interruptible() to wait for complete transmission,
but do not check the result of wait_event_interruptible() which can be
interrupted. It will result in TX buffer has multiple accessors and
the later process interferes with the previous process.

Following is one of the problems reported by syzbot.

=============================================================
WARNING: CPU: 0 PID: 0 at net/can/isotp.c:840 isotp_tx_timer_handler+0x2e0/0x4c0
CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.13.0-rc7+ #68
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1 04/01/2014
RIP: 0010:isotp_tx_timer_handler+0x2e0/0x4c0
Call Trace:
 <IRQ>
 ? isotp_setsockopt+0x390/0x390
 __hrtimer_run_queues+0xb8/0x610
 hrtimer_run_softirq+0x91/0xd0
 ? rcu_read_lock_sched_held+0x4d/0x80
 __do_softirq+0xe8/0x553
 irq_exit_rcu+0xf8/0x100
 sysvec_apic_timer_interrupt+0x9e/0xc0
 </IRQ>
 asm_sysvec_apic_timer_interrupt+0x12/0x20

Add result check for wait_event_interruptible() in isotp_sendmsg()
to avoid multiple accessers for tx buffer.


Affected upstream versions: 5.10
Fixed upstream versions: 0, 5.10.76, 5.14.15, 5.15
Upstream repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
Upstream fix commit: 053bc12df0d6097c1126d0e14fa778a0a8faeb64