deardaniel/secdata-raw huggingface dataset:
CVE: CVE-2025-15247
Published: 2025-12-30
Description: A vulnerability was identified in gmg137 snap7-rs up to 153d3e8c16decd7271e2a5b2e3da4d6f68589424. Affected by this issue is the function snap7_rs::client::S7Client::download of the file client.rs. Such manipulation leads to heap-based buffer overflow. The attack can be executed remotely. The exploit is publicly available and might be used. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. The project was informed of the problem early through an issue report but has not responded yet.
CVSS Score: 7.3 (HIGH)
CWE: CWE-119, CWE-122
References: https://gitee.com/gmg137/snap7-rs/; https://gitee.com/gmg137/snap7-rs/issues/ID2H7V; https://vuldb.com/?ctiid.338637
CVE: CVE-2022-50597
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50598
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50599
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50600
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50601
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50602
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50603
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50604
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50605
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50606
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50607
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50608
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50609
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50610
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50611
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50612
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50613
Published: 2025-12-30
Description: Rejected reason: ** REJECT ** DO NOT USE THIS CVE RECORD. ConsultIDs: none. Reason: This record was in a CNA pool that was not assigned to any issues during 2022. Notes: none.
CVE: CVE-2022-50809
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

xhci: dbc: Fix memory leak in xhci_alloc_dbc()

If DbC is already in use, then the allocated memory for the xhci_dbc struct
doesn't get freed before returning NULL, which leads to a memleak.
References: https://git.kernel.org/stable/c/103b459590e1eb4d80b02761eb36c7cae1d9b58e; https://git.kernel.org/stable/c/116d6a6964986ea7eb516daa36128d270f1f248d; https://git.kernel.org/stable/c/69e67c804d09a6b1bcda1f4f242f151f813eeb4a
CVE: CVE-2022-50810
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

rapidio: devices: fix missing put_device in mport_cdev_open

When kfifo_alloc fails, the refcount of chdev->dev is left incremental. 
We should use put_device(&chdev->dev) to decrease the ref count of
chdev->dev to avoid refcount leak.
References: https://git.kernel.org/stable/c/162433a96079bfa5ec748c486b4570f138d04fb5; https://git.kernel.org/stable/c/53915ecc43c5139d6cdd1caa4fdc9290b9597008; https://git.kernel.org/stable/c/6e4540e0970030e140998ce8847f5f0171b5afa1
CVE: CVE-2022-50811
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

erofs: fix missing unmap if z_erofs_get_extent_compressedlen() fails

Otherwise, meta buffers could be leaked.
References: https://git.kernel.org/stable/c/091a8ca572a2e48554427feda78aa503e98c1028; https://git.kernel.org/stable/c/373b6f350aecf5dca2e7474f0b4ec8cca659f2f0; https://git.kernel.org/stable/c/d5d188b8f8b38d3d71dd05993874b4fc9284ce95
CVE: CVE-2022-50812
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

security: Restrict CONFIG_ZERO_CALL_USED_REGS to gcc or clang > 15.0.6

A bad bug in clang's implementation of -fzero-call-used-regs can result
in NULL pointer dereferences (see the links above the check for more
information). Restrict CONFIG_CC_HAS_ZERO_CALL_USED_REGS to either a
supported GCC version or a clang newer than 15.0.6, which will catch
both a theoretical 15.0.7 and the upcoming 16.0.0, which will both have
the bug fixed.
References: https://git.kernel.org/stable/c/0b202dfedb5aa2e7d07d849be33fa3a48c026926; https://git.kernel.org/stable/c/21ca0bfa11bbb9a9207f5d2104f47d3d71b4616e; https://git.kernel.org/stable/c/8a4236456a3a402f6bb92aa7b75e7a3b4ef7a72c
CVE: CVE-2022-50813
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

drivers: mcb: fix resource leak in mcb_probe()

When probe hook function failed in mcb_probe(), it doesn't put the device.
Compiled test only.
References: https://git.kernel.org/stable/c/0468a585710bbb807a1b9c31df54bcf564d28b2b; https://git.kernel.org/stable/c/0a23dda78946f604ff752fe223c3c1f4fa6dd7b4; https://git.kernel.org/stable/c/0d1c2c8db28919c4351000d7c1692f1767bdc4f7
CVE: CVE-2022-50814
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

crypto: hisilicon/zip - fix mismatch in get/set sgl_sge_nr

KASAN reported this Bug:

	[17619.659757] BUG: KASAN: global-out-of-bounds in param_get_int+0x34/0x60
	[17619.673193] Read of size 4 at addr fffff01332d7ed00 by task read_all/1507958
	...
	[17619.698934] The buggy address belongs to the variable:
	[17619.708371]  sgl_sge_nr+0x0/0xffffffffffffa300 [hisi_zip]

There is a mismatch in hisi_zip when get/set the variable sgl_sge_nr.
The type of sgl_sge_nr is u16, and get/set sgl_sge_nr by
param_get/set_int.

Replacing param_get/set_int to param_get/set_ushort can fix this bug.
References: https://git.kernel.org/stable/c/[PII_REDACTED]05261c4e07a2fc97c2d1e53cd56819; https://git.kernel.org/stable/c/5eaebd19fbb0e26e73a34f55d3b1dc310df0eb15; https://git.kernel.org/stable/c/d74f9340097a881869c4c22ca376654cc2516ecc
CVE: CVE-2022-50815
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

ext2: Add sanity checks for group and filesystem size

Add sanity check that filesystem size does not exceed the underlying
device size and that group size is big enough so that metadata can fit
into it. This avoid trying to mount some crafted filesystems with
extremely large group counts.
References: https://git.kernel.org/stable/c/[PII_REDACTED]63998076b75e0c802524e2218a7d97; https://git.kernel.org/stable/c/40ff52527daec00cf1530c17a95636916ddd3b38; https://git.kernel.org/stable/c/d766f2d1e3e3bd44024a7f971ffcf8b8fbb7c5d2
CVE: CVE-2022-50816
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

ipv6: ensure sane device mtu in tunnels

Another syzbot report [1] with no reproducer hints
at a bug in ip6_gre tunnel (dev:ip6gretap0)

Since ipv6 mcast code makes sure to read dev->mtu once
and applies a sanity check on it (see commit b9b312a7a451
"ipv6: mcast: better catch silly mtu values"), a remaining
possibility is that a layer is able to set dev->mtu to
an underflowed value (high order bit set).

This could happen indeed in ip6gre_tnl_link_config_route(),
ip6_tnl_link_config() and ipip6_tunnel_bind_dev()

Make sure to sanitize mtu value in a local variable before
it is written once on dev->mtu, as lockless readers could
catch wrong temporary value.

[1]
skbuff: skb_over_panic: text:ffff80000b7a2f38 len:40 put:40 head:ffff000149dcf200 data:ffff000149dcf2b0 tail:0xd8 end:0xc0 dev:ip6gretap0
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:120
Internal error: Oops - BUG: 00000000f2000800 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 10241 Comm: kworker/1:1 Not tainted 6.0.0-rc7-syzkaller-18095-gbbed346d5a96 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/30/2022
Workqueue: mld mld_ifc_work
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : skb_panic+0x4c/0x50 net/core/skbuff.c:116
lr : skb_panic+0x4c/0x50 net/core/skbuff.c:116
sp : ffff800020dd3b60
x29: ffff800020dd3b70 x28: [PII_REDACTED] x27: ffff00010df2a800
x26:[PII_REDACTED]0000c0 x25:[PII_REDACTED]0000b0 x24: ffff000149dcf200
x23:[PII_REDACTED]0000c0 x22:[PII_REDACTED]0000d8 x21: ffff80000b7a2f38
x20: ffff00014c2f7800 x19: [PII_REDACTED] x18:[PII_REDACTED]0001a9
x17: [PII_REDACTED] x16: ffff80000db49158 x15: ffff000113bf1a80
x14: [PII_REDACTED] x13: 00000000ffffffff x12: ffff000113bf1a80
x11: ff808000081c0d5c x10: [PII_REDACTED] x9 : 73f125dc5c63ba00
x8 : 73f125dc5c63ba00 x7 : ffff800008161d1c x6 : [PII_REDACTED]
x5 : [PII_REDACTED] x4 : [PII_REDACTED] x3 : [PII_REDACTED]
x2 : ffff0001fefddcd0 x1 : [PII_REDACTED] x0 : [PII_REDACTED]
Call trace:
skb_panic+0x4c/0x50 net/core/skbuff.c:116
skb_over_panic net/core/skbuff.c:125 [inline]
skb_put+0xd4/0xdc net/core/skbuff.c:2049
ip6_mc_hdr net/ipv6/mcast.c:1714 [inline]
mld_newpack+0x14c/0x270 net/ipv6/mcast.c:1765
add_grhead net/ipv6/mcast.c:1851 [inline]
add_grec+0xa20/0xae0 net/ipv6/mcast.c:1989
mld_send_cr+0x438/0x5a8 net/ipv6/mcast.c:2115
mld_ifc_work+0x38/0x290 net/ipv6/mcast.c:2653
process_one_work+0x2d8/0x504 kernel/workqueue.c:2289
worker_thread+0x340/0x610 kernel/workqueue.c:2436
kthread+0x12c/0x158 kernel/kthread.c:376
ret_from_fork+0x10/0x20 arch/arm64/kernel/entry.S:860
Code: 91011400 aa0803e1 a90027ea 94373093 (d4210000)
References: https://git.kernel.org/stable/c/2bab6fa449d16af36d9c9518865f783a15f446c7; https://git.kernel.org/stable/c/44affe7ede596f078c4f2f41e0d160266ccda818; https://git.kernel.org/stable/c/78297d513157a31fd629626fe4cbb85a7dcbb94a
CVE: CVE-2022-50817
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

net: hsr: avoid possible NULL deref in skb_clone()

syzbot got a crash [1] in skb_clone(), caused by a bug
in hsr_get_untagged_frame().

When/if create_stripped_skb_hsr() returns NULL, we must
not attempt to call skb_clone().

While we are at it, replace a WARN_ONCE() by netdev_warn_once().

[1]
general protection fault, probably for non-canonical address 0xdffffc000000000f: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x[PII_REDACTED]000078-0x[PII_REDACTED]00007f]
CPU: 1 PID: 754 Comm: syz-executor.0 Not tainted 6.0.0-syzkaller-02734-g0326074ff465 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/22/2022
RIP: 0010:skb_clone+0x108/0x3c0 net/core/skbuff.c:1641
Code: 93 02 00 00 49 83 7c 24 28 00 0f 85 e9 00 00 00 e8 5d 4a 29 fa 4c 8d 75 7e 48 b8 00 00 00 00 00 fc ff df 4c 89 f2 48 c1 ea 03 <0f> b6 04 02 4c 89 f2 83 e2 07 38 d0 7f 08 84 c0 0f 85 9e 01 00 00
RSP: 0018:ffffc90003ccf4e0 EFLAGS: 00010207

RAX: dffffc[PII_REDACTED] RBX: ffffc90003ccf5f8 RCX: ffffc9000c24b000
RDX:[PII_REDACTED]00000f RSI: ffffffff8751cb13 RDI: [PII_REDACTED]
RBP: [PII_REDACTED] R08:[PII_REDACTED]0000f0 R09: [PII_REDACTED]
R10: fffffbfff181d972 R11: [PII_REDACTED] R12: ffff888161fc3640
R13:[PII_REDACTED]000a20 R14:[PII_REDACTED]00007e R15: ffffffff8dc5f620
FS: 00007feb621e4700(0000) GS:ffff8880b9b00000(0000) knlGS:[PII_REDACTED]
CS: 0010 DS: 0000 ES: 0000 CR0: [PII_REDACTED]
CR2: 00007feb621e3ff8 CR3:[PII_REDACTED]3a9000 CR4:[PII_REDACTED]3506e0
DR0: [PII_REDACTED] DR1: [PII_REDACTED] DR2: [PII_REDACTED]
DR3: [PII_REDACTED] DR6: 00000000fffe0ff0 DR7: [PII_REDACTED]
Call Trace:
<TASK>
hsr_get_untagged_frame+0x4e/0x610 net/hsr/hsr_forward.c:164
hsr_forward_do net/hsr/hsr_forward.c:461 [inline]
hsr_forward_skb+0xcca/0x1d50 net/hsr/hsr_forward.c:623
hsr_handle_frame+0x588/0x7c0 net/hsr/hsr_slave.c:69
__netif_receive_skb_core+0x9fe/0x38f0 net/core/dev.c:5379
__netif_receive_skb_one_core+0xae/0x180 net/core/dev.c:5483
__netif_receive_skb+0x1f/0x1c0 net/core/dev.c:5599
netif_receive_skb_internal net/core/dev.c:5685 [inline]
netif_receive_skb+0x12f/0x8d0 net/core/dev.c:5744
tun_rx_batched+0x4ab/0x7a0 drivers/net/tun.c:1544
tun_get_user+0x2686/0x3a00 drivers/net/tun.c:1995
tun_chr_write_iter+0xdb/0x200 drivers/net/tun.c:2025
call_write_iter include/linux/fs.h:2187 [inline]
new_sync_write fs/read_write.c:491 [inline]
vfs_write+0x9e9/0xdd0 fs/read_write.c:584
ksys_write+0x127/0x250 fs/read_write.c:637
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
References: https://git.kernel.org/stable/c/35ece858660eae13ee0242496a1956c39d29418e; https://git.kernel.org/stable/c/c46f2e0fcd1ecfc6046e5cf785ff89f0572f94e4; https://git.kernel.org/stable/c/d8b57135fd9ffe9a5b445350a686442a531c5339
CVE: CVE-2022-50818
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

scsi: pm8001: Fix running_req for internal abort commands

Disabling the remote phy for a SATA disk causes a hang:

root@(none)$ more /sys/class/sas_phy/phy-0:0:8/target_port_protocols
sata
root@(none)$ echo 0 > sys/class/sas_phy/phy-0:0:8/enable
root@(none)$ [   67.855950] sas: ex 500e004aaaaaaa1f phy08 change count has changed
[   67.920585] sd 0:0:2:0: [sdc] Synchronizing SCSI cache
[   67.925780] sd 0:0:2:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK
[   67.935094] sd 0:0:2:0: [sdc] Stopping disk
[   67.939305] sd 0:0:2:0: [sdc] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK
...
[  123.998998] INFO: task kworker/u192:1:642 blocked for more than 30 seconds.
[  124.005960]   Not tainted 6.0.0-rc1-205202-gf26f8f761e83 #218
[  124.012049] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[  124.019872] task:kworker/u192:1  state:D stack:0 pid:  642 ppid: 2 flags:0x00000008
[  124.028223] Workqueue: 0000:04:00.0_event_q sas_port_event_worker
[  124.034319] Call trace:
[  124.036758]  __switch_to+0x128/0x278
[  124.040333]  __schedule+0x434/0xa58
[  124.043820]  schedule+0x94/0x138
[  124.047045]  schedule_timeout+0x2fc/0x368
[  124.051052]  wait_for_completion+0xdc/0x200
[  124.055234]  __flush_workqueue+0x1a8/0x708
[  124.059328]  sas_porte_broadcast_rcvd+0xa8/0xc0
[  124.063858]  sas_port_event_worker+0x60/0x98
[  124.068126]  process_one_work+0x3f8/0x660
[  124.072134]  worker_thread+0x70/0x700
[  124.075793]  kthread+0x1a4/0x1b8
[  124.079014]  ret_from_fork+0x10/0x20

The issue is that the per-device running_req read in
pm8001_dev_gone_notify() never goes to zero and we never make progress.
This is caused by missing accounting for running_req for when an internal
abort command completes.

In commit 2cbbf489778e ("scsi: pm8001: Use libsas internal abort support")
we started to send internal abort commands as a proper sas_task. In this
when we deliver a sas_task to HW the per-device running_req is incremented
in pm8001_queue_command(). However it is never decremented for internal
abort commnds, so decrement in pm8001_mpi_task_abort_resp().
References: https://git.kernel.org/stable/c/4e750e0d8e486569fcb7f4ba6f6471673ce7d8a2; https://git.kernel.org/stable/c/a62b9fc9775fbc8e666bb328f6e53c168054d6fe; https://git.kernel.org/stable/c/d8c22c4697c11ed28062afe3c2b377025be11a23
CVE: CVE-2022-50820
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

perf/arm_dmc620: Fix hotplug callback leak in dmc620_pmu_init()

dmc620_pmu_init() won't remove the callback added by
cpuhp_setup_state_multi() when platform_driver_register() failed. Remove
the callback by cpuhp_remove_multi_state() in fail path.

Similar to the handling of arm_ccn_init() in commit 26242b330093 ("bus:
arm-ccn: Prevent hotplug callback leak")
References: https://git.kernel.org/stable/c/adf7c3bbcc819db6e95b6a61c9822230f0ef4778; https://git.kernel.org/stable/c/af170afa97e50d4169cfaa7ff4ec5d[PII_REDACTED]; https://git.kernel.org/stable/c/b99fbe8d949a99fe456f08c7aad421327685aa50
CVE: CVE-2022-50821
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

SUNRPC: Don't leak netobj memory when gss_read_proxy_verf() fails
References: https://git.kernel.org/stable/c/2cd6026e257362f030c8be57abaf7fc0049df60a; https://git.kernel.org/stable/c/67eb848161c2799f2007968ea3bc87adb15c9567; https://git.kernel.org/stable/c/76f2497a2faa6a4e91efb94a7f55705b403273fd
CVE: CVE-2022-50822
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

RDMA/restrack: Release MR restrack when delete

The MR restrack also needs to be released when delete it, otherwise it
cause memory leak as the task struct won't be released.
References: https://git.kernel.org/stable/c/13586753ae55146269a6dc8b216f17d86b81560c; https://git.kernel.org/stable/c/37c90753079fc95d93cc31b79796dd2ae57ad018; https://git.kernel.org/stable/c/8731cb5c7820bef577bab4ff17691fbf61c671cb
CVE: CVE-2022-50823
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

clk: tegra: Fix refcount leak in tegra114_clock_init

of_find_matching_node() returns a node pointer with refcount
incremented, we should use of_node_put() on it when not need anymore.
Add missing of_node_put() to avoid refcount leak.
References: https://git.kernel.org/stable/c/1f0e1cbbaffd729560716e9592aa5e609ea93bb6; https://git.kernel.org/stable/c/5984b1d66126b024ee77482602ac6e51b53f4116; https://git.kernel.org/stable/c/8cc87a9c142ae0e276a3ff9ce50f78a1668da36f
CVE: CVE-2022-50824
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

tpm: tpm_tis: Add the missed acpi_put_table() to fix memory leak

In check_acpi_tpm2(), we get the TPM2 table just to make
sure the table is there, not used after the init, so the
acpi_put_table() should be added to release the ACPI memory.
References: https://git.kernel.org/stable/c/3b6c822238da9ee[PII_REDACTED]601bcc603d49cb5; https://git.kernel.org/stable/c/43135fb098126ef2cd6ed584900fd7bfa25f95ce; https://git.kernel.org/stable/c/8bc6c10d3f389693410adb14b4e9deec01ff6334
CVE: CVE-2022-50825
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

usb: typec: wusb3801: fix fwnode refcount leak in wusb3801_probe()

I got the following report while doing fault injection test:

  OF: ERROR: memory leak, expected refcount 1 instead of 4,
  of_node_get()/of_node_put() unbalanced - destroy cset entry:
  attach overlay node /i2c/tcpc@60/connector

If wusb3801_hw_init() fails, fwnode_handle_put() needs be called to
avoid refcount leak.
References: https://git.kernel.org/stable/c/82d1211f673bbdc822eaf1dbcbf1f2ae06556964; https://git.kernel.org/stable/c/dc18a4c7b3bd447cef2395deeb1f6ac16dfaca0e; https://git.kernel.org/stable/c/de1e2eb7f102e[PII_REDACTED]414592a39efb66b3e
CVE: CVE-2022-50826
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

ipu3-imgu: Fix NULL pointer dereference in imgu_subdev_set_selection()

Calling v4l2_subdev_get_try_crop() and v4l2_subdev_get_try_compose()
with a subdev state of NULL leads to a NULL pointer dereference. This
can currently happen in imgu_subdev_set_selection() when the state
passed in is NULL, as this method first gets pointers to both the "try"
and "active" states and only then decides which to use.

The same issue has been addressed for imgu_subdev_get_selection() with
commit 30d03a0de650 ("ipu3-imgu: Fix NULL pointer dereference in active
selection access"). However the issue still persists in
imgu_subdev_set_selection().

Therefore, apply a similar fix as done in the aforementioned commit to
imgu_subdev_set_selection(). To keep things a bit cleaner, introduce
helper functions for "crop" and "compose" access and use them in both
imgu_subdev_set_selection() and imgu_subdev_get_selection().
References: https://git.kernel.org/stable/c/5038ee677606106c91564f9c4557d808d14bad70; https://git.kernel.org/stable/c/611d617bdb6c5d636a9861ec1c98e813fc8a5556; https://git.kernel.org/stable/c/dc608edf7d45ba0c2ad14c06eccd66474fec7847
CVE: CVE-2022-50827
Published: 2025-12-30
Description: In the Linux kernel, the following vulnerability has been resolved:

scsi: lpfc: Fix memory leak in lpfc_create_port()

Commit 5e633302ace1 ("scsi: lpfc: vmid: Add support for VMID in mailbox
command") introduced allocations for the VMID resources in
lpfc_create_port() after the call to scsi_host_alloc(). Upon failure on the
VMID allocations, the new code would branch to the 'out' label, which
returns NULL without unwinding anything, thus skipping the call to
scsi_host_put().

Fix the problem by creating a separate label 'out_free_vmid' to unwind the
VMID resources and make the 'out_put_shost' label call only
scsi_host_put(), as was done before the introduction of allocations for
VMID.
References: https://git.kernel.org/stable/c/5ea1f195f51c2bb5915ccfb2b2885ca81ce9262b; https://git.kernel.org/stable/c/9749595feb33a1a2b[PII_REDACTED]24ffeed5346b4; https://git.kernel.org/stable/c/dc8e483f684a24cc06e1d5fa958b54db58855093