deardaniel/secdata-raw huggingface dataset:
CVE: CVE-2025-22136
Published: 2025-01-08
Description: Tabby (formerly Terminus) is a highly configurable terminal emulator. Prior to 1.0.217 , Tabby enables several high-risk Electron Fuses, including RunAsNode, EnableNodeCliInspectArguments, and EnableNodeOptionsEnvironmentVariable. These fuses create potential code injection vectors even though the application is signed with hardened runtime and lacks dangerous entitlements such as com.apple.security.cs.disable-library-validation and com.apple.security.cs.allow-dyld-environment-variables. This vulnerability is fixed in 1.0.217.
CWE: CWE-94
References: https://github.com/Eugeny/tabby/commit/93513541f7161fa8a59491603cabb6a101c0c08e; https://github.com/Eugeny/tabby/security/advisories/GHSA-prcj-7rvc-26h4
CVE: CVE-2025-22137
Published: 2025-01-08
Description: Pingvin Share is a self-hosted file sharing platform and an alternative for WeTransfer. This vulnerability allows an authenticated or unauthenticated (if anonymous shares are allowed) user to overwrite arbitrary files on the server, including sensitive system files, via HTTP POST requests. The issue has been patched in version 1.4.0.
CVSS Score: 9.8 (CRITICAL)
CWE: CWE-20, CWE-434
References: https://github.com/stonith404/pingvin-share/commit/6cf5c66fe2eda1e0a525edf7440d047fe2f0e35b; https://github.com/stonith404/pingvin-share/commit/c52ec7192080c402bd804e69be93dd88cc7c5c70; https://github.com/stonith404/pingvin-share/security/advisories/GHSA-rjwx-p44f-mcrv
CVE: CVE-2024-13187
Published: 2025-01-08
Description: A vulnerability was found in Kingsoft WPS Office 6.14.0 on macOS. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component TCC Handler. The manipulation leads to code injection. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Score: 5.3 (MEDIUM)
CWE: CWE-74, CWE-94
References: https://github.com/Rsec-1/wps; https://vuldb.com/?ctiid.290779; https://vuldb.com/?id.290779
CVE: CVE-2024-55459
Published: 2025-01-08
Description: An issue in keras 3.7.0 allows attackers to write arbitrary files to the user's machine via downloading a crafted tar file through the get_file function.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-494
References: https://github.com/keras-team/keras; https://keras.io; https://river-bicycle-f1e.notion.site/Arbitrary-File-Write-Vulnerability-in-get_file-function-11888e[PII_REDACTED]9224e50892976d32
CVE: CVE-2025-20166
Published: 2025-01-08
Description: A vulnerability in the web-based management interface of Cisco Common Services Platform Collector (CSPC) could allow an authenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface.

This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected system. An attacker could exploit this vulnerability by injecting malicious code into specific pages of the interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. To exploit this vulnerability, the attacker must have at least a low-privileged account on an affected device.
Cisco has not released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
CVSS Score: 5.4 (MEDIUM)
CWE: CWE-86
References: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cspc-xss-CDOJZyH; https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-xwork-xss-KCcg7WwU
CVE: CVE-2025-20167
Published: 2025-01-08
Description: A vulnerability in the web-based management interface of Cisco Common Services Platform Collector (CSPC) could allow an authenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface.

This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected system. An attacker could exploit this vulnerability by injecting malicious code into specific pages of the interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. To exploit this vulnerability, the attacker must have at least a low-privileged account on an affected device.
Cisco has not released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
CVSS Score: 5.4 (MEDIUM)
CWE: CWE-86
References: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cspc-xss-CDOJZyH; https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-xwork-xss-KCcg7WwU
CVE: CVE-2025-20168
Published: 2025-01-08
Description: A vulnerability in the web-based management interface of Cisco Common Services Platform Collector (CSPC) could allow an authenticated, remote attacker to conduct cross-site scripting (XSS) attacks against a user of the interface.

This vulnerability is due to insufficient validation of user-supplied input by the web-based management interface of an affected system. An attacker could exploit this vulnerability by injecting malicious code into specific pages of the interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the affected interface or access sensitive, browser-based information. To exploit this vulnerability, the attacker must have at least a low-privileged account on an affected device.
Cisco has not released software updates that address this vulnerability. There are no workarounds that address this vulnerability.
CVSS Score: 5.4 (MEDIUM)
CWE: CWE-86
References: https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-cspc-xss-CDOJZyH; https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-xwork-xss-KCcg7WwU
CVE: CVE-2023-35685
Published: 2025-01-08
Description: In DevmemIntMapPages of devicemem_server.c, there is a possible physical page uaf due to a logic error in the code. This could lead to local escalation of privilege in the kernel with no additional execution privileges needed. User interaction is not needed for exploitation.
CVSS Score: 7.8 (HIGH)
CWE: CWE-416
References: https://issuetracker.google.com/issues/42420027
CVE: CVE-2024-51442
Published: 2025-01-08
Description: Command Injection in Minidlna version v1.3.3 and before allows an attacker to execute arbitrary OS commands via a specially crafted minidlna.conf configuration file.
CVSS Score: 8.8 (HIGH)
CWE: CWE-77
References: https://github.com/mselbrede/CVE-2024-51442; https://sourceforge.net/p/minidlna/bugs/364/; https://sourceforge.net/p/minidlna/git/ci/master/tree/minidlna.c
CVE: CVE-2024-56771
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

mtd: spinand: winbond: Fix 512GW, 01GW, 01JW and 02JW ECC information

These four chips:
* W25N512GW
* W25N01GW
* W25N01JW
* W25N02JW
all require a single bit of ECC strength and thus feature an on-die
Hamming-like ECC engine. There is no point in filling a ->get_status()
callback for them because the main ECC status bytes are located in
standard places, and retrieving the number of bitflips in case of
corrected chunk is both useless and unsupported (if there are bitflips,
then there is 1 at most, so no need to query the chip for that).

Without this change, a kernel warning triggers every time a bit flips.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/234d5f75c3ae911b52c5e4442b8a87fbbd129836; https://git.kernel.org/stable/c/fee9b240916df82a8b07aef0fdfe96785417a164
CVE: CVE-2024-56772
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

kunit: string-stream: Fix a UAF bug in kunit_init_suite()

In kunit_debugfs_create_suite(), if alloc_string_stream() fails in the
kunit_suite_for_each_test_case() loop, the "suite->log = stream"
has assigned before, and the error path only free the suite->log's stream
memory but not set it to NULL, so the later string_stream_clear() of
suite->log in kunit_init_suite() will cause below UAF bug.

Set stream pointer to NULL after free to fix it.

	Unable to handle kernel paging request at virtual address[PII_REDACTED]00030d
	Mem abort info:
	  ESR = 0x[PII_REDACTED]000004
	  EC = 0x25: DABT (current EL), IL = 32 bits
	  SET = 0, FnV = 0
	  EA = 0, S1PTW = 0
	  FSC = 0x04: level 0 translation fault
	Data abort info:
	  ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000
	  CM = 0, WnR = 0, TnD = 0, TagAccess = 0
	  GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
	[[PII_REDACTED]00030d] address between user and kernel address ranges
	Internal error: Oops: [PII_REDACTED] [#1] PREEMPT SMP
	Dumping ftrace buffer:
	   (ftrace buffer empty)
	Modules linked in: iio_test_gts industrialio_gts_helper cfg80211 rfkill ipv6 [last unloaded: iio_test_gts]
	CPU: 5 UID: 0 PID: 6253 Comm: modprobe Tainted: G    B   W        N 6.12.0-rc4+ #458
	Tainted: [B]=BAD_PAGE, [W]=WARN, [N]=TEST
	Hardware name: linux,dummy-virt (DT)
	pstate: 40000005 (nZcv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
	pc : string_stream_clear+0x54/0x1ac
	lr : string_stream_clear+0x1a8/0x1ac
	sp : ffffffc080b47410
	x29: ffffffc080b47410 x28:[PII_REDACTED]00030d x27: ffffff80c96b5e98
	x26: ffffff80c96b5e80 x25: ffffffe461b3f6c0 x24: [PII_REDACTED]
	x23: ffffff80c96b5e88 x22: 1ffffff019cdf4fc x21: dfffffc000000000
	x20: ffffff80ce6fa7e0 x19: 032202a80000186d x18: [PII_REDACTED]
	x17: [PII_REDACTED] x16: [PII_REDACTED] x15: ffffffe45c355cb4
	x14: ffffffe45c35589c x13: ffffffe45c03da78 x12: ffffffb810168e75
	x11: 1ffffff810168e74 x10: ffffffb810168e74 x9 : dfffffc000000000
	x8 : [PII_REDACTED] x7 : [PII_REDACTED] x6 : [PII_REDACTED]
	x5 : ffffffc080b473a0 x4 : [PII_REDACTED] x3 : [PII_REDACTED]
	x2 : [PII_REDACTED] x1 : ffffffe462fbf620 x0 : dfffffc000000000
	Call trace:
	 string_stream_clear+0x54/0x1ac
	 __kunit_test_suites_init+0x108/0x1d8
	 kunit_exec_run_tests+0xb8/0x100
	 kunit_module_notify+0x400/0x55c
	 notifier_call_chain+0xfc/0x3b4
	 blocking_notifier_call_chain+0x68/0x9c
	 do_init_module+0x24c/0x5c8
	 load_module+0x4acc/0x4e90
	 init_module_from_file+0xd4/0x128
	 idempotent_init_module+0x2d4/0x57c
	 __arm64_sys_finit_module+0xac/0x100
	 invoke_syscall+0x6c/0x258
	 el0_svc_common.constprop.0+0x160/0x22c
	 do_el0_svc+0x44/0x5c
	 el0_svc+0x48/0xb8
	 el0t_64_sync_handler+0x13c/0x158
	 el0t_64_sync+0x190/0x194
	Code: f9400753 d2dff800 f2fbffe0 d343fe7c (38e06b80)
	---[ end trace [PII_REDACTED] ]---
	Kernel panic - not syncing: Oops: Fatal exception
CVSS Score: 7.8 (HIGH)
CWE: CWE-416, CWE-416
References: https://git.kernel.org/stable/c/3213b92754b94dec6836e8b4d6ec7d224a805b61; https://git.kernel.org/stable/c/39e21403c978862846fa68b7f6d06f9cca235194
CVE: CVE-2024-56773
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

kunit: Fix potential null dereference in kunit_device_driver_test()

kunit_kzalloc() may return a NULL pointer, dereferencing it without
NULL check may lead to NULL dereference.
Add a NULL check for test_state.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/435c20eed572a95709b1536ff78832836b2f91b1; https://git.kernel.org/stable/c/5d28fac59369b5d3c48cdf09e50275a61ff91202
CVE: CVE-2024-56774
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

btrfs: add a sanity check for btrfs root in btrfs_search_slot()

Syzbot reports a null-ptr-deref in btrfs_search_slot().

The reproducer is using rescue=ibadroots, and the extent tree root is
corrupted thus the extent tree is NULL.

When scrub tries to search the extent tree to gather the needed extent
info, btrfs_search_slot() doesn't check if the target root is NULL or
not, resulting the null-ptr-deref.

Add sanity check for btrfs root before using it in btrfs_search_slot().
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/3ed51857a50f530ac7a1482e069dfbd1298558d4; https://git.kernel.org/stable/c/757171d1369b3b47f36932d40a05a0715496dcab; https://git.kernel.org/stable/c/93992c3d9629b02dccf[PII_REDACTED]d5c24f2dece
CVE: CVE-2024-56775
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Fix handling of plane refcount

[Why]
The mechanism to backup and restore plane states doesn't maintain
refcount, which can cause issues if the refcount of the plane changes
in between backup and restore operations, such as memory leaks if the
refcount was supposed to go down, or double frees / invalid memory
accesses if the refcount was supposed to go up.

[How]
Cache and re-apply current refcount when restoring plane states.
CVSS Score: 7.8 (HIGH)
CWE: CWE-401, CWE-415, CWE-415
References: https://git.kernel.org/stable/c/27227a234c1487cb7a684615f0749c455218833a; https://git.kernel.org/stable/c/8cb2f6793845f135b28361ba8e96901cae3e5790
CVE: CVE-2024-56776
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/sti: avoid potential dereference of error pointers

The return value of drm_atomic_get_crtc_state() needs to be
checked. To avoid use of error pointer 'crtc_state' in case
of the failure.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-754, CWE-754
References: https://git.kernel.org/stable/c/40725c5fabee804fecce41d4d5c5bae80c45e1c4; https://git.kernel.org/stable/c/831214f77037de02afc287eae93ce97f218d8c04; https://git.kernel.org/stable/c/8ab73ac97c0fa528f66eeccd9bb53eb6eb7d20dc
CVE: CVE-2024-56777
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/sti: avoid potential dereference of error pointers in sti_gdp_atomic_check

The return value of drm_atomic_get_crtc_state() needs to be
checked. To avoid use of error pointer 'crtc_state' in case
of the failure.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-754, CWE-754
References: https://git.kernel.org/stable/c/3cf2e7c448e246f7e700c7aa47450d1e27579559; https://git.kernel.org/stable/c/997b64c3f4c1827c5cfda8ae7f5d13f78d28b541; https://git.kernel.org/stable/c/b79612ed6bc1a184c45427105c851b5b2d4342ca
CVE: CVE-2024-56778
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/sti: avoid potential dereference of error pointers in sti_hqvdp_atomic_check

The return value of drm_atomic_get_crtc_state() needs to be
checked. To avoid use of error pointer 'crtc_state' in case
of the failure.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-754, CWE-754
References: https://git.kernel.org/stable/c/31c857e7496d34e5a32a6f75bc024d0b06fd646a; https://git.kernel.org/stable/c/6b0d0d6e9d3c26697230bf7dc9e6b52bdb24086f; https://git.kernel.org/stable/c/82a5312f874fb18f045d9658e9bd290e3b0621c0
CVE: CVE-2024-56780
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

quota: flush quota_release_work upon quota writeback

One of the paths quota writeback is called from is:

freeze_super()
  sync_filesystem()
    ext4_sync_fs()
      dquot_writeback_dquots()

Since we currently don't always flush the quota_release_work queue in
this path, we can end up with the following race:

 1. dquot are added to releasing_dquots list during regular operations.
 2. FS Freeze starts, however, this does not flush the quota_release_work queue.
 3. Freeze completes.
 4. Kernel eventually tries to flush the workqueue while FS is frozen which
    hits a WARN_ON since transaction gets started during frozen state:

  ext4_journal_check_start+0x28/0x110 [ext4] (unreliable)
  __ext4_journal_start_sb+0x64/0x1c0 [ext4]
  ext4_release_dquot+0x90/0x1d0 [ext4]
  quota_release_workfn+0x43c/0x4d0

Which is the following line:

  WARN_ON(sb->s_writers.frozen == SB_FREEZE_COMPLETE);

Which ultimately results in generic/390 failing due to dmesg
noise. This was detected on powerpc machine 15 cores.

To avoid this, make sure to flush the workqueue during
dquot_writeback_dquots() so we dont have any pending workitems after
freeze.
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/3e6ff207cd5bd924ad94cd1a7c633bcdac0ba1cb; https://git.kernel.org/stable/c/6f3821acd7c[PII_REDACTED]248087de5fb4b48cf26; https://git.kernel.org/stable/c/8ea87e[PII_REDACTED]5d290f4dc5216276e91cb224
CVE: CVE-2024-56781
Published: 2025-01-08
Description: Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE: CVE-2024-56782
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

ACPI: x86: Add adev NULL check to acpi_quirk_skip_serdev_enumeration()

acpi_dev_hid_match() does not check for adev == NULL, dereferencing
it unconditional.

Add a check for adev being NULL before calling acpi_dev_hid_match().

At the moment acpi_quirk_skip_serdev_enumeration() is never called with
a controller_parent without an ACPI companion, but better safe than sorry.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-476, CWE-476
References: https://git.kernel.org/stable/c/4a49194f587a62d972b602e3e1a2c3cfe6567966; https://git.kernel.org/stable/c/e173bce05f7032a8b4964cfef82a4b7668f5f3af
CVE: CVE-2024-56783
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

netfilter: nft_socket: remove WARN_ON_ONCE on maximum cgroup level

cgroup maximum depth is INT_MAX by default, there is a cgroup toggle to
restrict this maximum depth to a more reasonable value not to harm
performance. Remove unnecessary WARN_ON_ONCE which is reachable from
userspace.
CVSS Score: 5.5 (MEDIUM)
CWE: CWE-617, CWE-617
References: https://git.kernel.org/stable/c/2f9bec0a749eb646b384fde0c7b7c24687b2ffae; https://git.kernel.org/stable/c/7064a6daa4a700a298fe3aee11dea296bfe59fc4; https://git.kernel.org/stable/c/b7529880cb961d515642ce63f9d7570869bbbdc3
CVE: CVE-2024-56784
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

drm/amd/display: Adding array index check to prevent memory corruption

[Why & How]
Array indices out of bound caused memory corruption. Adding checks to
ensure that array index stays in bound.
CVSS Score: 7.8 (HIGH)
CWE: CWE-787, CWE-787
References: https://git.kernel.org/stable/c/2c437d9a0b496168e1a1defd17b531f0a526dbe9; https://git.kernel.org/stable/c/dff526dc3e27f5484f5ba11471b9fbbe681467f2
CVE: CVE-2024-56785
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

MIPS: Loongson64: DTS: Really fix PCIe port nodes for ls7a

Fix the dtc warnings:

    arch/mips/boot/dts/loongson/ls7a-pch.dtsi:68.16-416.5: Warning (interrupt_provider): /bus@10000000/pci@1a000000: '#interrupt-cells' found, but node is not an interrupt provider
    arch/mips/boot/dts/loongson/ls7a-pch.dtsi:68.16-416.5: Warning (interrupt_provider): /bus@10000000/pci@1a000000: '#interrupt-cells' found, but node is not an interrupt provider
    arch/mips/boot/dts/loongson/loongson64g_4core_ls7a.dtb: Warning (interrupt_map): Failed prerequisite 'interrupt_provider'

And a runtime warning introduced in commit 045b14ca5c36 ("of: WARN on
deprecated #address-cells/#size-cells handling"):

    WARNING: CPU: 0 PID: 1 at drivers/of/base.c:106 of_bus_n_addr_cells+0x9c/0xe0
    Missing '#address-cells' in /bus@10000000/pci@1a000000/pci_bridge@9,0

The fix is similar to commit d89a415ff8d5 ("MIPS: Loongson64: DTS: Fix PCIe
port nodes for ls7a"), which has fixed the issue for ls2k (despite its
subject mentions ls7a).
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/01575f2ff8ba578a3436f230668bd056dc2eb823; https://git.kernel.org/stable/c/4fbd66d8254cedfd1218393f39d83b6c07a01917; https://git.kernel.org/stable/c/5a2eaa3ad2b803c7ea442c6db7379466ee73c024
CVE: CVE-2024-56786
Published: 2025-01-08
Description: Rejected reason: This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
CVE: CVE-2024-56787
Published: 2025-01-08
Description: In the Linux kernel, the following vulnerability has been resolved:

soc: imx8m: Probe the SoC driver as platform driver

With driver_async_probe=* on kernel command line, the following trace is
produced because on i.MX8M Plus hardware because the soc-imx8m.c driver
calls of_clk_get_by_name() which returns -EPROBE_DEFER because the clock
driver is not yet probed. This was not detected during regular testing
without driver_async_probe.

Convert the SoC code to platform driver and instantiate a platform device
in its current device_initcall() to probe the platform driver. Rework
.soc_revision callback to always return valid error code and return SoC
revision via parameter. This way, if anything in the .soc_revision callback
return -EPROBE_DEFER, it gets propagated to .probe and the .probe will get
retried later.

"
------------[ cut here ]------------
WARNING: CPU: 1 PID: 1 at drivers/soc/imx/soc-imx8m.c:115 imx8mm_soc_revision+0xdc/0x180
CPU: 1 UID: 0 PID: 1 Comm: swapper/0 Not tainted 6.11.0-next-20[PII_REDACTED]2-g2062bb554dea #603
Hardware name: DH electronics i.MX8M Plus DHCOM Premium Developer Kit (3) (DT)
pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : imx8mm_soc_revision+0xdc/0x180
lr : imx8mm_soc_revision+0xd0/0x180
sp : ffff8000821fbcc0
x29: ffff8000821fbce0 x28: [PII_REDACTED] x27: ffff[PII_REDACTED]20
x26: ffff8000818a9970 x25: [PII_REDACTED] x24: [PII_REDACTED]
x23: ffff8000817f42c8 x22: ffff0000df8be210 x21: fffffffffffffdfb
x20: ffff[PII_REDACTED]00 x19: [PII_REDACTED] x18: ffffffffffffffff
x17: ffff800081fff418 x16: ffff8000823e1000 x15: ffff0000c03b65e8
x14: ffff0000c00051b0 x13: ffff[PII_REDACTED]00 x12: [PII_REDACTED]
x11: ffff80008278ffff x10: ffff80008209d3a6 x9 : ffff80008062e95c
x8 : ffff8000821fb9a0 x7 : [PII_REDACTED] x6 :[PII_REDACTED]0080e3
x5 : ffff0000df8c03d8 x4 : [PII_REDACTED] x3 : [PII_REDACTED]
x2 : [PII_REDACTED] x1 : fffffffffffffdfb x0 : fffffffffffffdfb
Call trace:
 imx8mm_soc_revision+0xdc/0x180
 imx8_soc_init+0xb0/0x1e0
 do_one_initcall+0x94/0x1a8
 kernel_init_freeable+0x240/0x2a8
 kernel_init+0x28/0x140
 ret_from_fork+0x10/0x20
---[ end trace [PII_REDACTED] ]---
SoC: i.MX8MP revision 1.1
"
CVSS Score: 5.5 (MEDIUM)
References: https://git.kernel.org/stable/c/2129f6faa5dfe8c6b87aad11720bf75edd77d3e4; https://git.kernel.org/stable/c/997a3c04d7fa3d1d385c14691350d096fada648c; https://git.kernel.org/stable/c/9cc832d37799dbea950c4c8a34721b02b8b5a8ff
CVE: CVE-2024-6350
Published: 2025-01-08
Description: A malformed 802.15.4 packet causes a buffer overflow to occur leading to an assert and a denial of service. A watchdog reset clears the error condition automatically.
CVSS Score: 6.5 (MEDIUM)
CWE: CWE-120
References: https://community.silabs.com/069Vm00000HtvDgIAJ; https://github.com/SiliconLabs/simplicity_sdk/releases
CVE: CVE-2025-21111
Published: 2025-01-08
Description: Dell VxRail, versions 8.0.000 through 8.0.311, contain(s) a Plaintext Storage of a Password vulnerability. A high privileged attacker with local access could potentially exploit this vulnerability, leading to Information exposure.
CVSS Score: 7.5 (HIGH)
CWE: CWE-256, CWE-522
References: https://www.dell.com/support/kbdoc/en-us/000269958/dsa-2025-025-security-update-for-dell-vxrail-for-multiple-vulnerabilities
CVE: CVE-2024-13188
Published: 2025-01-08
Description: A vulnerability was found in MicroWorld eScan Antivirus 7.0.32 on Linux. It has been rated as critical. Affected by this issue is some unknown functionality of the file /opt/MicroWorld/var/ of the component Installation Handler. The manipulation leads to incorrect default permissions. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Score: 5.3 (MEDIUM)
CWE: CWE-266, CWE-276
References: https://github.com/hawkteam404/RnD_Public/blob/main/escan_incorrect_default_perm.md; https://vuldb.com/?ctiid.290780; https://vuldb.com/?id.290780