deardaniel/secdata-raw huggingface dataset:
CVE: CVE-2024-13012
Published: 2024-12-29
Description: A vulnerability, which was classified as problematic, has been found in code-projects Hostel Management System 1.0. This issue affects some unknown processing of the file /admin/registration.php. The manipulation of the argument fname/mname/lname leads to cross site scripting. The attack may be initiated remotely.
CVSS Score: 3.5 (LOW)
CWE: CWE-79, CWE-94, CWE-79
References: https://code-projects.org/; https://vuldb.com/?ctiid.289703; https://vuldb.com/?id.289703
CVE: CVE-2024-56720
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

bpf, sockmap: Several fixes to bpf_msg_pop_data

Several fixes to bpf_msg_pop_data,
1. In sk_msg_shift_left, we should put_page
2. if (len == 0), return early is better
3. pop the entire sk_msg (last == msg->sg.size) should be supported
4. Fix for the value of variable "a"
5. In sk_msg_shift_left, after shifting, i has already pointed to the next
element. Addtional sk_msg_iter_var_next may result in BUG.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-193, CWE-401, CWE-401
References: https://git.kernel.org/stable/c/275a9f3ef8fabb0cb282a62b9e164dedba7284c5; https://git.kernel.org/stable/c/5d609ba262475db450ba69b8e8a557bd768ac07a; https://git.kernel.org/stable/c/785180bed9879680d8e5c5e1b54c8ae8d948f4c8
CVE: CVE-2024-56721
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

x86/CPU/AMD: Terminate the erratum_1386_microcode array

The erratum_1386_microcode array requires an empty entry at the end.
Otherwise x86_match_cpu_with_stepping() will continue iterate the array after
it ended.

Add an empty entry to erratum_1386_microcode to its end.
CVSS Score: 7.1 (HIGH)
CWE: CWE-125, CWE-125
References: https://git.kernel.org/stable/c/82d6b82cf89d950982ac240ba068c3a7e1f23b0a; https://git.kernel.org/stable/c/ccfee14f08b8699132b87bc6d78e0fa75bf094dd; https://git.kernel.org/stable/c/ff6cdc407f4179748f4673c39b[PII_REDACTED]a0ad
CVE: CVE-2024-56722
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

RDMA/hns: Fix cpu stuck caused by printings during reset

During reset, cmd to destroy resources such as qp, cq, and mr may fail,
and error logs will be printed. When a large number of resources are
destroyed, there will be lots of printings, and it may lead to a cpu
stuck.

Delete some unnecessary printings and replace other printing functions
in these paths with the ratelimited version.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-770, CWE-770
References: https://git.kernel.org/stable/c/31c6fe9b79ed42440094f2367897aea0c0ce96ec; https://git.kernel.org/stable/c/323275ac2ff15b2b7b3eac391ae5d8c5a3c3a999; https://git.kernel.org/stable/c/a0e4c78770faa0d56d47391476fe1d827e72eded
CVE: CVE-2024-56723
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

mfd: intel_soc_pmic_bxtwc: Use IRQ domain for PMIC devices

While design wise the idea of converting the driver to use
the hierarchy of the IRQ chips is correct, the implementation
has (inherited) flaws. This was unveiled when platform_get_irq()
had started WARN() on IRQ 0 that is supposed to be a Linux
IRQ number (also known as vIRQ).

Rework the driver to respect IRQ domain when creating each MFD
device separately, as the domain is not the same for all of them.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/0350d783ab888cb1cb48ced36cc28b372723f1a4; https://git.kernel.org/stable/c/61d590d7076b50b6ebdea1f3b83bb041c01fc482; https://git.kernel.org/stable/c/6ea17c03edc7ed0aabb1431eb26e2f94849af68a
CVE: CVE-2024-56724
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

mfd: intel_soc_pmic_bxtwc: Use IRQ domain for TMU device

While design wise the idea of converting the driver to use
the hierarchy of the IRQ chips is correct, the implementation
has (inherited) flaws. This was unveiled when platform_get_irq()
had started WARN() on IRQ 0 that is supposed to be a Linux
IRQ number (also known as vIRQ).

Rework the driver to respect IRQ domain when creating each MFD
device separately, as the domain is not the same for all of them.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/1b734ad0e33648c3988c6a37c2ac16c2d63eda06; https://git.kernel.org/stable/c/2310f5336f32eac9ada2d59b965d578efe25c4bf; https://git.kernel.org/stable/c/56acf415772ee7e10e448b371f52b249aa2d0f7b
CVE: CVE-2024-56725
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_dcbnl.c

Add error pointer check after calling otx2_mbox_get_rsp().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-754, CWE-754
References: https://git.kernel.org/stable/c/54e8b501b3ea9371e4a9aa639c75b681fa5680f0; https://git.kernel.org/stable/c/69297b0d3369488af259e3a7cf53d69157938ea1; https://git.kernel.org/stable/c/6ee6cf42dc5230425cfce1ffefa5a8d8a99e6fce
CVE: CVE-2024-56726
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

octeontx2-pf: handle otx2_mbox_get_rsp errors in cn10k.c

Add error pointer check after calling otx2_mbox_get_rsp().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/41f39f4c67253f802809310be6846ff408c3c758; https://git.kernel.org/stable/c/54abcec092616a4d01195355eb5d6036fb8fe363; https://git.kernel.org/stable/c/856ad633e11869729be698df2287ecfe6ec31f27
CVE: CVE-2024-56727
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_flows.c

Adding error pointer check after calling otx2_mbox_get_rsp().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/8c9f8b35dc3d4ad8053a72bc0c5a7843591f6b75; https://git.kernel.org/stable/c/a479b3d7586e6f77f8337bbcac980eaf2d0a4029; https://git.kernel.org/stable/c/bd3110bc102ab6292656b8118be819faa0de8dd0
CVE: CVE-2024-56728
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

octeontx2-pf: handle otx2_mbox_get_rsp errors in otx2_ethtool.c

Add error pointer check after calling otx2_mbox_get_rsp().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-754, CWE-754
References: https://git.kernel.org/stable/c/05a6ce174c0c724e5914e1e5efd826bab8f382b4; https://git.kernel.org/stable/c/2db2194727b1f49a5096c1c3981adef1b7638733; https://git.kernel.org/stable/c/55c41b97001a09bb490ffa2e667e251d75d15ab1
CVE: CVE-2024-56729
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

smb: Initialize cfid->tcon before performing network ops

Avoid leaking a tcon ref when a lease break races with opening the
cached directory. Processing the leak break might take a reference to
the tcon in cached_dir_lease_break() and then fail to release the ref in
cached_dir_offload_close, since cfid->tcon is still NULL.
CVSS Score: 4.7 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/1b9ab6b648f89441c8a13cb3fd8ca83ffebc5262; https://git.kernel.org/stable/c/4b216c8f9c7d84ef7de33ca60b97e08e03ef3292; https://git.kernel.org/stable/c/625e2357c8fcfae6e66dcc667dc656fe390bab15
CVE: CVE-2024-56730
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

net/9p/usbg: fix handling of the failed kzalloc() memory allocation

On the linux-next, next-20241108 vanilla kernel, the coccinelle tool gave the
following error report:

./net/9p/trans_usbg.c:912:5-11: ERROR: allocation function on line 911 returns
NULL not ERR_PTR on failure

kzalloc() failure is fixed to handle the NULL return case on the memory exhaustion.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/2cdb416de8b5795fd25fadcb69e1198b6df6d8cc; https://git.kernel.org/stable/c/ff1060813d9347e8c45c8b8cff93a4dfdb6726ad
CVE: CVE-2024-56739
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

rtc: check if __rtc_read_time was successful in rtc_timer_do_work()

If the __rtc_read_time call fails,, the struct rtc_time tm; may contain
uninitialized data, or an illegal date/time read from the RTC hardware.

When calling rtc_tm_to_ktime later, the result may be a very large value
(possibly KTIME_MAX). If there are periodic timers in rtc->timerqueue,
they will continually expire, may causing kernel softlockup.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-908, CWE-908
References: https://git.kernel.org/stable/c/0d68e8514d9040108ff7d1b37ca71096674b6efe; https://git.kernel.org/stable/c/246f621d363988e7040f4546d20203dc713fa3e1; https://git.kernel.org/stable/c/39ad0a1ae17b54509cd9e93dcd8cec16e7c12d3f
CVE: CVE-2024-56740
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

nfs/localio: must clear res.replen in nfs_local_read_done

Otherwise memory corruption can occur due to NFSv3 LOCALIO reads
leaving garbage in res.replen:
- nfs3_read_done() copies that into server->read_hdrsize; from there
  nfs3_proc_read_setup() copies it to args.replen in new requests.
- nfs3_xdr_enc_read3args() passes that to rpc_prepare_reply_pages()
  which includes it in hdrsize for xdr_init_pages, so that rq_rcv_buf
  contains a ridiculous len.
- This is copied to rq_private_buf and xs_read_stream_request()
  eventually passes the kvec to sock_recvmsg() which receives incoming
  data into entirely the wrong place.

This is easily reproduced with NFSv3 LOCALIO that is servicing reads
when it is made to pivot back to using normal RPC.  This switch back
to using normal NFSv3 with RPC can occur for a few reasons but this
issue was exposed with a test that stops and then restarts the NFSv3
server while LOCALIO is performing heavy read IO.
CVSS Score: 7.8 (HIGH)
CWE: CWE-787, CWE-787
References: https://git.kernel.org/stable/c/650703bc4ed3edf841e851c99ab8e7ba9e5262a3; https://git.kernel.org/stable/c/de5dac261eeab99762bbdf7c20cee5d26ef4462e
CVE: CVE-2024-56741
Published: 2024-12-29
Description: Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE: CVE-2024-56742
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

vfio/mlx5: Fix an unwind issue in mlx5vf_add_migration_pages()

Fix an unwind issue in mlx5vf_add_migration_pages().

If a set of pages is allocated but fails to be added to the SG table,
they need to be freed to prevent a memory leak.

Any pages successfully added to the SG table will be freed as part of
mlx5vf_free_data_buffer().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/22e87bf3f77c18f5982c19ffe2732ef0c7a25f16; https://git.kernel.org/stable/c/769fe4ce444b646b0bf6ac308de80686c730c7df; https://git.kernel.org/stable/c/c44f1b2ddfa81c8d7f8e9b6bc76c427bc00e69d5
CVE: CVE-2024-56743
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

nfs_common: must not hold RCU while calling nfsd_file_put_local

Move holding the RCU from nfs_to_nfsd_file_put_local to
nfs_to_nfsd_net_put.  It is the call to nfs_to->nfsd_serv_put that
requires the RCU anyway (the puts for nfsd_file and netns were
combined to avoid an extra indirect reference but that
micro-optimization isn't possible now).

This fixes xfstests generic/013 and it triggering:

"Voluntary context switch within RCU read-side critical section!"

[  143.545738] Call Trace:
[  143.546206]  <TASK>
[  143.546625]  ? show_regs+0x6d/0x80
[  143.547267]  ? __warn+0x91/0x140
[  143.547951]  ? rcu_note_context_switch+0x496/0x5d0
[  143.548856]  ? report_bug+0x193/0x1a0
[  143.549557]  ? handle_bug+0x63/0xa0
[  143.550214]  ? exc_invalid_op+0x1d/0x80
[  143.550938]  ? asm_exc_invalid_op+0x1f/0x30
[  143.551736]  ? rcu_note_context_switch+0x496/0x5d0
[  143.552634]  ? wakeup_preempt+0x62/0x70
[  143.553358]  __schedule+0xaa/0x1380
[  143.554025]  ? _raw_spin_unlock_irqrestore+0x12/0x40
[  143.554958]  ? try_to_wake_up+0x1fe/0x6b0
[  143.555715]  ? wake_up_process+0x19/0x20
[  143.556452]  schedule+0x2e/0x120
[  143.557066]  schedule_preempt_disabled+0x19/0x30
[  143.557933]  rwsem_down_read_slowpath+0x24d/0x4a0
[  143.558818]  ? xfs_efi_item_format+0x50/0xc0 [xfs]
[  143.559894]  down_read+0x4e/0xb0
[  143.560519]  xlog_cil_commit+0x1b2/0xbc0 [xfs]
[  143.561460]  ? _raw_spin_unlock+0x12/0x30
[  143.562212]  ? xfs_inode_item_precommit+0xc7/0x220 [xfs]
[  143.563309]  ? xfs_trans_run_precommits+0x69/0xd0 [xfs]
[  143.564394]  __xfs_trans_commit+0xb5/0x330 [xfs]
[  143.565367]  xfs_trans_roll+0x48/0xc0 [xfs]
[  143.566262]  xfs_defer_trans_roll+0x57/0x100 [xfs]
[  143.567278]  xfs_defer_finish_noroll+0x27a/0x490 [xfs]
[  143.568342]  xfs_defer_finish+0x1a/0x80 [xfs]
[  143.569267]  xfs_bunmapi_range+0x4d/0xb0 [xfs]
[  143.570208]  xfs_itruncate_extents_flags+0x13d/0x230 [xfs]
[  143.571353]  xfs_free_eofblocks+0x12e/0x190 [xfs]
[  143.572359]  xfs_file_release+0x12d/0x140 [xfs]
[  143.573324]  __fput+0xe8/0x2d0
[  143.573922]  __fput_sync+0x1d/0x30
[  143.574574]  nfsd_filp_close+0x33/0x60 [nfsd]
[  143.575430]  nfsd_file_free+0x96/0x150 [nfsd]
[  143.576274]  nfsd_file_put+0xf7/0x1a0 [nfsd]
[  143.577104]  nfsd_file_put_local+0x18/0x30 [nfsd]
[  143.578070]  nfs_close_local_fh+0x101/0x110 [nfs_localio]
[  143.579079]  __put_nfs_open_context+0xc9/0x180 [nfs]
[  143.580031]  nfs_file_clear_open_context+0x4a/0x60 [nfs]
[  143.581038]  nfs_file_release+0x3e/0x60 [nfs]
[  143.581879]  __fput+0xe8/0x2d0
[  143.582464]  __fput_sync+0x1d/0x30
[  143.583108]  __x64_sys_close+0x41/0x80
[  143.583823]  x64_sys_call+0x189a/0x20d0
[  143.584552]  do_syscall_64+0x64/0x170
[  143.585240]  entry_SYSCALL_64_after_hwframe+0x76/0x7e
[  143.586185] RIP: 0033:0x7f3c5153efd7
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-667, CWE-667
References: https://git.kernel.org/stable/c/3e6e3e97d64f50d9b6b1d62274f08925b1adbfc2; https://git.kernel.org/stable/c/c840b8e1f039e90f97ca55525667eb961422f86c
CVE: CVE-2024-56745
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

PCI: Fix reset_method_store() memory leak

In reset_method_store(), a string is allocated via kstrndup() and assigned
to the local "options". options is then used in with strsep() to find
spaces:

  while ((name = strsep(&options, " ")) != NULL) {

If there are no remaining spaces, then options is set to NULL by strsep(),
so the subsequent kfree(options) doesn't free the memory allocated via
kstrndup().

Fix by using a separate tmp_options to iterate with strsep() so options is
preserved.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/2985b1844f3f3447f2d938eff1ef[PII_REDACTED]a5; https://git.kernel.org/stable/c/403efb4457c0c8f8f51e904cc57d39193780c6bd; https://git.kernel.org/stable/c/543d0eb40e45c6a51f1bff02f417b602e54472d5
CVE: CVE-2024-56746
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

fbdev: sh7760fb: Fix a possible memory leak in sh7760fb_alloc_mem()

When information such as info->screen_base is not ready, calling
sh7760fb_free_mem() does not release memory correctly. Call
dma_free_coherent() instead.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/0d3fb3b3e9d66f7b6346e3b90bc0ff48683539ce; https://git.kernel.org/stable/c/29216bb390e36daeebef66abaa02d[PII_REDACTED]b; https://git.kernel.org/stable/c/3dd9df8e5f34c6fc4217a7498c1fb3c352d4afc2
CVE: CVE-2024-56747
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

scsi: qedi: Fix a possible memory leak in qedi_alloc_and_init_sb()

Hook "qedi_ops->common->sb_init = qed_sb_init" does not release the DMA
memory sb_virt when it fails. Add dma_free_coherent() to free it. This
is the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/10a6fc486ac40a410f0fb84cc15161238eccd20a; https://git.kernel.org/stable/c/20b775cf274cfbfa3da871a1108877e17b8b19e1; https://git.kernel.org/stable/c/4e48e5b26b3edc0e1dd329201ffc924a7a1f9337
CVE: CVE-2024-56748
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

scsi: qedf: Fix a possible memory leak in qedf_alloc_and_init_sb()

Hook "qed_ops->common->sb_init = qed_sb_init" does not release the DMA
memory sb_virt when it fails. Add dma_free_coherent() to free it. This
is the same way as qedr_alloc_mem_sb() and qede_alloc_mem_sb().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/0e04bd5a11dffe8c1c0e4c9fc79f7d3cd6182dd5; https://git.kernel.org/stable/c/64654bf5efb3f748e6fc41227adda689618ce9c4; https://git.kernel.org/stable/c/78a169dc69fbdaf114c40e2d56955bf6bd4fc3c0
CVE: CVE-2024-56749
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

dlm: fix dlm_recover_members refcount on error

If dlm_recover_members() fails we don't drop the references of the
previous created root_list that holds and keep all rsbs alive during the
recovery. It might be not an unlikely event because ping_members() could
run into an -EINTR if another recovery progress was triggered again.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/200b977ebbc313a59174ba971006a231b3533dc5; https://git.kernel.org/stable/c/3230718a75a6c30ed60ac920c26be2119fa82b8e; https://git.kernel.org/stable/c/fb2ec564887af1f365d754f7c306f1b5cd375b5e
CVE: CVE-2024-56750
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

erofs: fix blksize < PAGE_SIZE for file-backed mounts

Adjust sb->s_blocksize{,_bits} directly for file-backed
mounts when the fs block size is smaller than PAGE_SIZE.

Previously, EROFS used sb_set_blocksize(), which caused
a panic if bdev-backed mounts is not used.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/679d8537e5748241c71ac97a6b6dc919eae31716; https://git.kernel.org/stable/c/bae[PII_REDACTED]a64a092516ff1b2f221402b843b
CVE: CVE-2024-56751
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

ipv6: release nexthop on device removal

The CI is hitting some aperiodic hangup at device removal time in the
pmtu.sh self-test:

unregister_netdevice: waiting for veth_A-R1 to become free. Usage count = 6
ref_tracker: veth_A-R1@ffff888013df15d8 has 1/5 users at
	dst_init+0x84/0x4a0
	dst_alloc+0x97/0x150
	ip6_dst_alloc+0x23/0x90
	ip6_rt_pcpu_alloc+0x1e6/0x520
	ip6_pol_route+0x56f/0x840
	fib6_rule_lookup+0x334/0x630
	ip6_route_output_flags+0x259/0x480
	ip6_dst_lookup_tail.constprop.0+0x5c2/0x940
	ip6_dst_lookup_flow+0x88/0x190
	udp_tunnel6_dst_lookup+0x2a7/0x4c0
	vxlan_xmit_one+0xbde/0x4a50 [vxlan]
	vxlan_xmit+0x9ad/0xf20 [vxlan]
	dev_hard_start_xmit+0x10e/0x360
	__dev_queue_xmit+0xf95/0x18c0
	arp_solicit+0x4a2/0xe00
	neigh_probe+0xaa/0xf0

While the first suspect is the dst_cache, explicitly tracking the dst
owing the last device reference via probes proved such dst is held by
the nexthop in the originating fib6_info.

Similar to commit f5b51fe804ec ("ipv6: route: purge exception on
removal"), we need to explicitly release the originating fib info when
disconnecting a to-be-removed device from a live ipv6 dst: move the
fib6_info cleanup into ip6_dst_ifdown().

Tested running:

./pmtu.sh cleanup_ipv6_exception

in a tight loop for more than 400 iterations with no spat, running an
unpatched kernel  I observed a splat every ~10 iterations.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/0e4c6faaef8a24b762a24ffb767280e263ef8e10; https://git.kernel.org/stable/c/43e25adc80269f917d2a195f0d59f74cdd182955; https://git.kernel.org/stable/c/77aa9855a878fb43f547ddfbda3127a1e88ad31a
CVE: CVE-2024-56752
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/nouveau/gr/gf100: Fix missing unlock in gf100_gr_chan_new()

When the call to gf100_grctx_generate() fails, unlock gr->fecs.mutex
before returning the error.

Fixes smatch warning:

drivers/gpu/drm/nouveau/nvkm/engine/gr/gf100.c:480 gf100_gr_chan_new() warn: inconsistent returns '&gr->fecs.mutex'.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/22b4a623c0f230540f02f4358744cce62ae12dbf; https://git.kernel.org/stable/c/237f2dbfa00576bb1aa8dc2dce403c64e53270e6; https://git.kernel.org/stable/c/24b1df744ef444f9846f52de4985790a5fd1c0de
CVE: CVE-2024-56753
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu/gfx9: Add Cleaner Shader Deinitialization in gfx_v9_0 Module

This commit addresses an omission in the previous patch related to the
cleaner shader support for GFX9 hardware. Specifically, it adds the
necessary deinitialization code for the cleaner shader in the
gfx_v9_0_sw_fini function.

The added line amdgpu_gfx_cleaner_shader_sw_fini(adev); ensures that any
allocated resources for the cleaner shader are freed correctly, avoiding
potential memory leaks and ensuring that the GPU state is clean for the
next initialization sequence.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/720c0376b3d29cbab921a60062fda5980742ed9d; https://git.kernel.org/stable/c/e47cb9d2533200d49dd5364d4a148119492f8a3d
CVE: CVE-2024-56754
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

crypto: caam - Fix the pointer passed to caam_qi_shutdown()

The type of the last parameter given to devm_add_action_or_reset() is
"struct caam_drv_private *", but in caam_qi_shutdown(), it is casted to
"struct device *".

Pass the correct parameter to devm_add_action_or_reset() so that the
resources are released as expected.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/1f8e2f597b918ca5827a5c6d00b819d064264d1c; https://git.kernel.org/stable/c/6187727e57aec122c8a99c464c74578c810cbe40; https://git.kernel.org/stable/c/66eddb8dcb61065c[PII_REDACTED]5f14b54232bcc2
CVE: CVE-2024-56755
Published: 2024-12-29
Description: In the Linux kernel, the following vulnerability has been resolved:

netfs/fscache: Add a memory barrier for FSCACHE_VOLUME_CREATING

In fscache_create_volume(), there is a missing memory barrier between the
bit-clearing operation and the wake-up operation. This may cause a
situation where, after a wake-up, the bit-clearing operation hasn't been
detected yet, leading to an indefinite wait. The triggering process is as
follows:

  [cookie1]                [cookie2]                  [volume_work]
fscache_perform_lookup
  fscache_create_volume
                        fscache_perform_lookup
                          fscache_create_volume
			                        fscache_create_volume_work
                                                  cachefiles_acquire_volume
                                                  clear_and_wake_up_bit
    test_and_set_bit
                            test_and_set_bit
                              goto maybe_wait
      goto no_wait

In the above process, cookie1 and cookie2 has the same volume. When cookie1
enters the -no_wait- process, it will clear the bit and wake up the waiting
process. If a barrier is missing, it may cause cookie2 to remain in the
-wait- process indefinitely.

In commit 3288666c7256 ("fscache: Use clear_and_wake_up_bit() in
fscache_create_volume_work()"), barriers were added to similar operations
in fscache_create_volume_work(), but fscache_create_volume() was missed.

By combining the clear and wake operations into clear_and_wake_up_bit() to
fix this issue.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-401, CWE-401
References: https://git.kernel.org/stable/c/22f9400a6f[PII_REDACTED]e0a64247b8fcc811a24d; https://git.kernel.org/stable/c/539fabba965e119b98066fc6ba5257b5eaf4eda2; https://git.kernel.org/stable/c/8beb682cc9a0798a280bbb95e3e[PII_REDACTED]0b2