Kushalkhemka/embedding-cve-nvd-dataset huggingface dataset:
he regs struct instead as it is defined for all supported platforms. Note that it is ok setting the key reg even if that latter is disabled as the interrupt won't be enabled anyway. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/334d74a798463ceec02a41eb0e2354aaac0d6249 - https://git.kernel.org/stable/c/90fa6015ff83ef1c373cc61b7c924ab2bcbe1801 - https://git.kernel.org/stable/c/619c05fb176c272ac6cecf723446b39723ee6d97 - https://git.kernel.org/stable/c/09429ddb5a91e9e8f72cd18c012ec4171c2f85ec - https://git.kernel.org/stable/c/11cdb506d0fbf5ac05bf55f5afcb3a215c316490
CVE ID: CVE-2025-37973 State: PUBLISHED Published: 2025-05-20T16:47:19.074Z Last Updated: 2025-05-26T05:24:53.261Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: cfg80211: fix out-of-bounds access during multi-link element defragmentation Currently during the multi-link element defragmentation process, the multi-link element length added to the total IEs length when calculating the length of remaining IEs after the multi-link element in cfg80211_defrag_mle(). This could lead to out-of-bounds access if the multi-link element or its corresponding fragment elements are the last elements in the IEs buffer. To address this iss
e multi-link element or its corresponding fragment elements are the last elements in the IEs buffer. To address this issue, correctly calculate the remaining IEs length by deducting the multi-link element end offset from total IEs end offset. References: - https://git.kernel.org/stable/c/73dde269a1a43e6b1aa92eba13ad2df58bfdd38e - https://git.kernel.org/stable/c/9423f6da825172b8dc60d4688ed3d147291c3be9 - https://git.kernel.org/stable/c/e1c6d0c6199bd5f4cfc7a66ae7032b6e805f904d - https://git.kernel.org/stable/c/023c1f2f0609218103cbcb48e0104b144d4a16dc
CVE ID: CVE-2025-37974 State: PUBLISHED Published: 2025-05-20T16:47:19.676Z Last Updated: 2025-05-26T05:24:54.557Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: s390/pci: Fix missing check for zpci_create_device() error return The zpci_create_device() function returns an error pointer that needs to be checked before dereferencing it as a struct zpci_dev pointer. Add the missing check in __clp_add() where it was missed when adding the scan_list in the fixed commit. Simply not adding the device to the scan list results in the previous behavior. References: - https://git.kernel.org/stable/c/be54b750c333a9db7c3b3686846bb06b07b011f
results in the previous behavior. References: - https://git.kernel.org/stable/c/be54b750c333a9db7c3b3686846bb06b07b011fe - https://git.kernel.org/stable/c/2769b718e164df983c20c314b263a71a699be6cd - https://git.kernel.org/stable/c/42420c50c68f3e95e90de2479464f420602229fc
CVE ID: CVE-2025-37975 State: PUBLISHED Published: 2025-05-20T16:58:19.270Z Last Updated: 2025-05-26T05:24:55.886Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: riscv: module: Fix out-of-bounds relocation access The current code allows rel[j] to access one element past the end of the relocation section. Simplify to num_relocations which is equivalent to the existing size expression. References: - https://git.kernel.org/stable/c/a068ea00009d373d825c528f9c168501519211b4 - https://git.kernel.org/stable/c/95e4e1c1cf614d125f159db9726b7abb32e18385 - https://git.kernel.org/stable/c/0b4cce68efb93e31a8e51795d696df6e379cb41c
CVE ID: CVE-2025-37976 State: REJECTED Published: 2025-05-20T16:58:19.992Z Last Updated: 2025-06-18T13:33:56.449Z Description: No description available.
CVE ID: CVE-2025-37977 State: PUBLISHED Published: 2025-05-20T16:58:20.693Z Last Updated: 2025-05-26T05:24:57.157Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: ufs: exynos: Disable iocc if dma-coherent property isn't set If dma-coherent property isn't set then descriptors are non-cacheable and the iocc shareability bits should be disabled. Without this UFS can end up in an incompatible configuration and suffer from random cache related stability issues. References: - https://git.kernel.org/stable/c/869749e48115ef944eeabec8e84138908471fa51 - https://git.kernel.org/stable/c/f0c6728a6f2e269ebb234a9b5bb6c2c24aafeb51 - https
749e48115ef944eeabec8e84138908471fa51 - https://git.kernel.org/stable/c/f0c6728a6f2e269ebb234a9b5bb6c2c24aafeb51 - https://git.kernel.org/stable/c/f92bb7436802f8eb7ee72dc911a33c8897fde366
CVE ID: CVE-2025-37978 State: PUBLISHED Published: 2025-05-20T16:58:21.422Z Last Updated: 2025-05-26T05:24:58.426Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: block: integrity: Do not call set_page_dirty_lock() Placing multiple protection information buffers inside the same page can lead to oopses because set_page_dirty_lock() can't be called from interrupt context. Since a protection information buffer is not backed by a file there is no point in setting its page dirty, there is nothing to synchronize. Drop the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec(). References: - https://gi
p the call to set_page_dirty_lock() and remove the last argument to bio_integrity_unpin_bvec(). References: - https://git.kernel.org/stable/c/c38a005e6efb9ddfa06bd8353b82379d6fd5d6c4 - https://git.kernel.org/stable/c/9487fc1a10b3aa89feb24e7cedeccaaf63074617 - https://git.kernel.org/stable/c/39e160505198ff8c158f11bce2ba19809a756e8b
CVE ID: CVE-2025-37979 State: PUBLISHED Published: 2025-05-20T16:58:22.103Z Last Updated: 2025-11-03T19:57:56.701Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: ASoC: qcom: Fix sc7280 lpass potential buffer overflow Case values introduced in commit 5f78e1fb7a3e ("ASoC: qcom: Add driver support for audioreach solution") cause out of bounds access in arrays of sc7280 driver data (e.g. in case of RX_CODEC_DMA_RX_0 in sc7280_snd_hw_params()). Redefine LPASS_MAX_PORTS to consider the maximum possible port id for q6dsp as sc7280 driver utilizes some of those values. Found by Linux Verification Center (linuxtesting.org) with SVACE. A
6dsp as sc7280 driver utilizes some of those values. Found by Linux Verification Center (linuxtesting.org) with SVACE. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/d78888853eb53f47ae16cf3aa5d0444d0331b9f8 - https://git.kernel.org/stable/c/a12c14577882b1f2b4cff0f86265682f16e97b0c - https://git.kernel.org/stable/c/c0ce01e0ff8a0d61a7b089ab309cdc12bc527c39 - https://git.kernel.org/stable/c/b807b7c81a6d066757a94af7b8fa5b6a37e4d0b3 - https://git.kernel.org/stable/c/a31a4934b31faea76e735bab17e63d02fcd8e029
CVE ID: CVE-2025-37980 State: PUBLISHED Published: 2025-05-20T16:58:22.720Z Last Updated: 2025-05-26T05:25:00.874Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: block: fix resource leak in blk_register_queue() error path When registering a queue fails after blk_mq_sysfs_register() is successful but the function later encounters an error, we need to clean up the blk_mq_sysfs resources. Add the missing blk_mq_sysfs_unregister() call in the error path to properly clean up these resources and prevent a memory leak. References: - https://git.kernel.org/stable/c/549cbbd14bbec12469ceb279b79c763c8a24224e - https://git.kernel.org/stabl
k. References: - https://git.kernel.org/stable/c/549cbbd14bbec12469ceb279b79c763c8a24224e - https://git.kernel.org/stable/c/41e43134ddda35949974be40520460a12dda3502 - https://git.kernel.org/stable/c/55a7bb2708f7c7c5b366d4e40916113168a3824c - https://git.kernel.org/stable/c/40f2eb9b531475dd01b683fdaf61ca3cfd03a51e
CVE ID: CVE-2025-37981 State: PUBLISHED Published: 2025-05-20T16:58:23.299Z Last Updated: 2025-05-26T05:25:02.522Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Use is_kdump_kernel() to check for kdump The smartpqi driver checks the reset_devices variable to determine whether special adjustments need to be made for kdump. This has the effect that after a regular kexec reboot, some driver parameters such as max_transfer_size are much lower than usual. More importantly, kexec reboot tests have revealed memory corruption caused by the driver log being written to system memory after a kexec. Fix this by testing is_
evealed memory corruption caused by the driver log being written to system memory after a kexec. Fix this by testing is_kdump_kernel() rather than reset_devices where appropriate. References: - https://git.kernel.org/stable/c/7cc670e8ebaa5241dd99c0ad75eceb8f8f64f607 - https://git.kernel.org/stable/c/ebf673c76ce91e612a882dfaa9a3824962994aae - https://git.kernel.org/stable/c/a2d5a0072235a69749ceb04c1a26dc75df66a31a
CVE ID: CVE-2025-37982 State: PUBLISHED Published: 2025-05-20T16:58:23.861Z Last Updated: 2025-11-03T19:57:58.118Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: wl1251: fix memory leak in wl1251_tx_work The skb dequeued from tx_queue is lost when wl1251_ps_elp_wakeup fails with a -ETIMEDOUT error. Fix that by queueing the skb back to tx_queue. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/13c9744c1bcdb5de4e7dc1a78784788ecec52add - https://git.kernel.org/stable/c/f08448a885403722c5c77dae51964badfcb69495 - https://git.kernel.org/stable/c/2996144be660d930d5e394652abe08fe89d
/stable/c/f08448a885403722c5c77dae51964badfcb69495 - https://git.kernel.org/stable/c/2996144be660d930d5e394652abe08fe89dbe00e - https://git.kernel.org/stable/c/8fd4b9551af214d037fbc9d8e179840b8b917841 - https://git.kernel.org/stable/c/4a43fd36710669d67dbb5c16287a58412582ca26 - https://git.kernel.org/stable/c/52f224009ce1e44805e6ff3ffc2a06af9c1c3c5b - https://git.kernel.org/stable/c/5a90c29d0204c5ffc45b43b4eced6eef0e19a33a - https://git.kernel.org/stable/c/a0f0dc96de03ffeefc2a177b7f8acde565cb77f4
CVE ID: CVE-2025-37983 State: PUBLISHED Published: 2025-05-20T17:09:17.666Z Last Updated: 2025-11-03T19:57:59.628Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: qibfs: fix _another_ leak failure to allocate inode => leaked dentry... this one had been there since the initial merge; to be fair, if we are that far OOM, the odds of failing at that particular allocation are low... Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/5e280cce3a29b7fe7b828c6ccd5aa5ba87ceb6b6 - https://git.kernel.org/stable/c/3c2fde33e3e505dfd1a895d1f24bad650c655e14 - https://git.kernel.org/stable/c/5fe708c5
b6 - https://git.kernel.org/stable/c/3c2fde33e3e505dfd1a895d1f24bad650c655e14 - https://git.kernel.org/stable/c/5fe708c5e3c8b2152c6caaa67243e431a5d6cca3 - https://git.kernel.org/stable/c/545defa656568c74590317cd30068f85134a8216 - https://git.kernel.org/stable/c/5d53e88d8370b9ab14dd830abb410d9a2671edb6 - https://git.kernel.org/stable/c/47ab2caba495c1d6a899d284e541a8df656dcfe9 - https://git.kernel.org/stable/c/24faa6ea274a2b96d0a78a0996c3137c2b2a65f0 - https://git.kernel.org/stable/c/bdb43af4fdb39f844ede401bdb1258f67a580a27
CVE ID: CVE-2025-37984 State: PUBLISHED Published: 2025-05-20T17:09:18.321Z Last Updated: 2025-07-25T13:44:56.640Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: crypto: ecdsa - Harden against integer overflows in DIV_ROUND_UP() Herbert notes that DIV_ROUND_UP() may overflow unnecessarily if an ecdsa implementation's ->key_size() callback returns an unusually large value. Herbert instead suggests (for a division by 8): X / 8 + !!(X & 7) Based on this formula, introduce a generic DIV_ROUND_UP_POW2() macro and use it in lieu of DIV_ROUND_UP() for ->key_size() return values. Additionally, use the macro in ecc_digits_from_bytes(),
se it in lieu of DIV_ROUND_UP() for ->key_size() return values. Additionally, use the macro in ecc_digits_from_bytes(), whose "nbytes" parameter is a ->key_size() return value in some instances, or a user-specified ASN.1 length in the case of ecdsa_get_signature_rs(). References: - https://git.kernel.org/stable/c/f02f0218be412cff1c844addf58e002071be298b - https://git.kernel.org/stable/c/f2133b849ff273abddb6da622daddd8f6f6fa448 - https://git.kernel.org/stable/c/921b8167f10708e38080f84e195cdc68a7a561f1 - https://git.kernel.org/stable/c/b16510a530d1e6ab9683f04f8fb34f2e0f538275
CVE ID: CVE-2025-37985 State: PUBLISHED Published: 2025-05-20T17:09:18.963Z Last Updated: 2025-11-03T19:58:01.024Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: USB: wdm: close race between wdm_open and wdm_wwan_port_stop Clearing WDM_WWAN_IN_USE must be the last action or we can open a chardev whose URBs are still poisoned Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/b02a3fef3e8c8fe5a0a266f7a14f38cc608fb167 - https://git.kernel.org/stable/c/217fe1fc7d112595a793e02b306710e702eac492 - https://git.kernel.org/stable/c/54f7f8978af19f899dec80bcc71c8d4855dfbd72 - https://git.kernel
a793e02b306710e702eac492 - https://git.kernel.org/stable/c/54f7f8978af19f899dec80bcc71c8d4855dfbd72 - https://git.kernel.org/stable/c/52ae15c665b5fe5876655aaccc3ef70560b0e314 - https://git.kernel.org/stable/c/e3c9adc69357fcbe6253a2bc2588ee4bbaaedbe9 - https://git.kernel.org/stable/c/c1846ed4eb527bdfe6b3b7dd2c78e2af4bf98f4f
CVE ID: CVE-2025-37986 State: PUBLISHED Published: 2025-05-20T17:09:19.584Z Last Updated: 2025-05-26T05:25:08.944Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: usb: typec: class: Invalidate USB device pointers on partner unregistration To avoid using invalid USB device pointers after a Type-C partner disconnects, this patch clears the pointers upon partner unregistration. This ensures a clean state for future connections. References: - https://git.kernel.org/stable/c/40966fc9939e85677fdb489dfddfa205baaad03b - https://git.kernel.org/stable/c/74911338f47c13d1b9470fc50718182bffad42e2 - https://git.kernel.org/stable/c/66e1a887273
- https://git.kernel.org/stable/c/74911338f47c13d1b9470fc50718182bffad42e2 - https://git.kernel.org/stable/c/66e1a887273c6b89f09bc11a40d0a71d5a081a8e
CVE ID: CVE-2025-37987 State: PUBLISHED Published: 2025-05-20T17:09:20.166Z Last Updated: 2025-06-04T12:57:38.445Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: pds_core: Prevent possible adminq overflow/stuck condition The pds_core's adminq is protected by the adminq_lock, which prevents more than 1 command to be posted onto it at any one time. This makes it so the client drivers cannot simultaneously post adminq commands. However, the completions happen in a different context, which means multiple adminq commands can be posted sequentially and all waiting on completion. On the FW side, the backing adminq request queue is onl
mmands can be posted sequentially and all waiting on completion. On the FW side, the backing adminq request queue is only 16 entries long and the retry mechanism and/or overflow/stuck prevention is lacking. This can cause the adminq to get stuck, so commands are no longer processed and completions are no longer sent by the FW. As an initial fix, prevent more than 16 outstanding adminq commands so there's no way to cause the adminq from getting stuck. This works because the backing adminq request queue will never have more than 16 pending adminq commands, so it will never overflow. This is done by reducing the adminq depth to 16. References: - https://git.kernel.org/stable/c/517f928cc0c133472
erflow. This is done by reducing the adminq depth to 16. References: - https://git.kernel.org/stable/c/517f928cc0c133472618cbba18382b46f5f71ba3 - https://git.kernel.org/stable/c/2982e07ad72b48eb12c29a87a3f2126ea552688c - https://git.kernel.org/stable/c/5e3dc65675faad846420d24762e4faadc12d9392 - https://git.kernel.org/stable/c/d9e2f070d8af60f2c8c02b2ddf0a9e90b4e9220c
CVE ID: CVE-2025-37988 State: PUBLISHED Published: 2025-05-20T17:09:20.765Z Last Updated: 2025-05-26T05:25:11.548Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: fix a couple of races in MNT_TREE_BENEATH handling by do_move_mount() Normally do_lock_mount(path, _) is locking a mountpoint pinned by *path and at the time when matching unlock_mount() unlocks that location it is still pinned by the same thing. Unfortunately, for 'beneath' case it's no longer that simple - the object being locked is not the one *path points to. It's the mountpoint of path->mnt. The thing is, without sufficient locking ->mnt_parent may change under us
h points to. It's the mountpoint of path->mnt. The thing is, without sufficient locking ->mnt_parent may change under us and none of the locks are held at that point. The rules are * mount_lock stabilizes m->mnt_parent for any mount m. * namespace_sem stabilizes m->mnt_parent, provided that m is mounted. * if either of the above holds and refcount of m is positive, we are guaranteed the same for refcount of m->mnt_parent. namespace_sem nests inside inode_lock(), so do_lock_mount() has to take inode_lock() before grabbing namespace_sem. It does recheck that path->mnt is still mounted in the same place after getting namespace_sem, and it does take care to pin the dentry. It is needed, since ot
l mounted in the same place after getting namespace_sem, and it does take care to pin the dentry. It is needed, since otherwise we might end up with racing mount --move (or umount) happening while we were getting locks; in that case dentry would no longer be a mountpoint and could've been evicted on memory pressure along with its inode - not something you want when grabbing lock on that inode. However, pinning a dentry is not enough - the matching mount is also pinned only by the fact that path->mnt is mounted on top it and at that point we are not holding any locks whatsoever, so the same kind of races could end up with all references to that mount gone just as we are about to enter inode_l
ver, so the same kind of races could end up with all references to that mount gone just as we are about to enter inode_lock(). If that happens, we are left with filesystem being shut down while we are holding a dentry reference on it; results are not pretty. What we need to do is grab both dentry and mount at the same time; that makes inode_lock() safe *and* avoids the problem with fs getting shut down under us. After taking namespace_sem we verify that path->mnt is still mounted (which stabilizes its ->mnt_parent) and check that it's still mounted at the same place. From that point on to the matching namespace_unlock() we are guaranteed that mount/dentry pair we'd grabbed are also pinned by
hat point on to the matching namespace_unlock() we are guaranteed that mount/dentry pair we'd grabbed are also pinned by being the mountpoint of path->mnt, so we can quietly drop both the dentry reference (as the current code does) and mnt one - it's OK to do under namespace_sem, since we are not dropping the final refs. That solves the problem on do_lock_mount() side; unlock_mount() also has one, since dentry is guaranteed to stay pinned only until the namespace_unlock(). That's easy to fix - just have inode_unlock() done earlier, while it's still pinned by mp->m_dentry. References: - https://git.kernel.org/stable/c/4f435c1f4c48ff84968e2d9159f6fa41f46cf998 - https://git.kernel.org/stable/c/
eferences: - https://git.kernel.org/stable/c/4f435c1f4c48ff84968e2d9159f6fa41f46cf998 - https://git.kernel.org/stable/c/a61afd54826ac24c2c93845c4f441dbc344875b1 - https://git.kernel.org/stable/c/d4b21e8cd3d7efa2deb9cff534f0133e84f35086 - https://git.kernel.org/stable/c/0d039eac6e5950f9d1ecc9e410c2fd1feaeab3b6
CVE ID: CVE-2025-37989 State: PUBLISHED Published: 2025-05-20T17:09:21.419Z Last Updated: 2025-11-03T19:58:02.430Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: net: phy: leds: fix memory leak A network restart test on a router led to an out-of-memory condition, which was traced to a memory leak in the PHY LED trigger code. The root cause is misuse of the devm API. The registration function (phy_led_triggers_register) is called from phy_attach_direct, not phy_probe, and the unregister function (phy_led_triggers_unregister) is called from phy_detach, not phy_remove. This means the register and unregister functions can be called
rs_unregister) is called from phy_detach, not phy_remove. This means the register and unregister functions can be called multiple times for the same PHY device, but devm-allocated memory is not freed until the driver is unbound. This also prevents kmemleak from detecting the leak, as the devm API internally stores the allocated pointer. Fix this by replacing devm_kzalloc/devm_kcalloc with standard kzalloc/kcalloc, and add the corresponding kfree calls in the unregister path. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/966d6494e2ed9be9052fcd9815afba830896aaf8 - https://git.kernel.org/stable/c/95bed65cc0eb2a610550abf849a8b94374da80a7 - https
d6494e2ed9be9052fcd9815afba830896aaf8 - https://git.kernel.org/stable/c/95bed65cc0eb2a610550abf849a8b94374da80a7 - https://git.kernel.org/stable/c/663c3da86e807c6c07ed48f911c7526fad6fe1ff - https://git.kernel.org/stable/c/f41f097f68a33d392579885426d0734a81219501 - https://git.kernel.org/stable/c/618541a6cc1511064dfa58c89b3445e21844092f - https://git.kernel.org/stable/c/41143e71052a00d654c15dc924fda50c1e7357d0 - https://git.kernel.org/stable/c/7f3d5880800f962c347777c4f8358f29f5fc403c - https://git.kernel.org/stable/c/b7f0ee992adf601aa00c252418266177eb7ac2bc
CVE ID: CVE-2025-37990 State: PUBLISHED Published: 2025-05-20T17:18:45.366Z Last Updated: 2025-11-03T19:58:03.822Z Vendors: Linux Products: Linux Description: In the Linux kernel, the following vulnerability has been resolved: wifi: brcm80211: fmac: Add error handling for brcmf_usb_dl_writeimage() The function brcmf_usb_dl_writeimage() calls the function brcmf_usb_dl_cmd() but dose not check its return value. The 'state.state' and the 'state.bytes' are uninitialized if the function brcmf_usb_dl_cmd() fails. It is dangerous to use uninitialized variables in the conditions. Add error handling for brcmf_usb_dl_cmd() to jump to error handling path if the brcmf_usb_dl_cmd() fails and the 'state.s
dd error handling for brcmf_usb_dl_cmd() to jump to error handling path if the brcmf_usb_dl_cmd() fails and the 'state.state' and the 'state.bytes' are uninitialized. Improve the error message to report more detailed error information. Additional Analyst Notes: - CVE Program Container: References: - https://git.kernel.org/stable/c/972bf75e53f778c78039c5d139dd47443a6d66a1 - https://git.kernel.org/stable/c/62a4f2955d9a1745bdb410bf83fb16666d8865d6 - https://git.kernel.org/stable/c/508be7c001437bacad7b9a43f08a723887bcd1ea - https://git.kernel.org/stable/c/524b70441baba453b193c418e3142bd31059cc1f - https://git.kernel.org/stable/c/08424a0922fb9e32a19b09d852ee87fb6c497538 - https://git.kernel.org/s
18e3142bd31059cc1f - https://git.kernel.org/stable/c/08424a0922fb9e32a19b09d852ee87fb6c497538 - https://git.kernel.org/stable/c/bdb435ef9815b1ae28eefffa01c6959d0fcf1fa7 - https://git.kernel.org/stable/c/fa9b9f02212574ee1867fbefb0a675362a71b31d - https://git.kernel.org/stable/c/8e089e7b585d95122c8122d732d1d5ef8f879396