Page 10 of 3967 results (0.006 seconds)

CVSS: -EPSS: 0%CPEs: 5EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: secretmem: disable memfd_secret() if arch cannot set direct map Return -ENOSYS from memfd_secret() syscall if !can_set_direct_map(). This is the case for example on some arm64 configurations, where marking 4k PTEs in the direct map not present can only be done if the direct map is set up at 4k granularity in the first place (as ARM's break-before-make semantics do not easily allow breaking apart large/gigantic pages). More precisely, on arm64 systems with !can_set_direct_map(), set_direct_map_invalid_noflush() is a no-op, however it returns success (0) instead of an error. This means that memfd_secret will seemingly "work" (e.g. • https://git.kernel.org/stable/c/1507f51255c9ff07d75909a84e7c0d7f3c4b2f49 https://git.kernel.org/stable/c/d0ae6ffa1aeb297aef89f49cfb894a83c329ebad https://git.kernel.org/stable/c/5ea0b7af38754d2b45ead9257bca47e84662e926 https://git.kernel.org/stable/c/7caf966390e6e4ebf42775df54e7ee1f280ce677 https://git.kernel.org/stable/c/757786abe4547eb3d9d0e8350a63bdb0f9824af2 https://git.kernel.org/stable/c/532b53cebe58f34ce1c0f34d866f5c0e335c53c6 •

CVSS: -EPSS: 0%CPEs: 6EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: clk: imx: Remove CLK_SET_PARENT_GATE for DRAM mux for i.MX7D For i.MX7D DRAM related mux clock, the clock source change should ONLY be done done in low level asm code without accessing DRAM, and then calling clk API to sync the HW clock status with clk tree, it should never touch real clock source switch via clk API, so CLK_SET_PARENT_GATE flag should NOT be added, otherwise, DRAM's clock parent will be disabled when DRAM is active, and system will hang. • https://git.kernel.org/stable/c/b677b94a9193ec7b6607bd1255172ae59174a382 https://git.kernel.org/stable/c/d18dc8e14b9c794f58dae1577ccb2ab84a4a1b11 https://git.kernel.org/stable/c/11ceb17e6f07cc30410f3a6276cddda248a9b863 https://git.kernel.org/stable/c/339273a9ddfe7632b717c2e13e81cbd5d383e1ff https://git.kernel.org/stable/c/94f6cdc837e38371324cee97dfd2ef1a99a82c98 https://git.kernel.org/stable/c/a54c441b46a0745683c2eef5a359d22856d27323 •

CVSS: -EPSS: 0%CPEs: 8EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: fbdev: sisfb: Fix strbuf array overflow The values of the variables xres and yres are placed in strbuf. These variables are obtained from strbuf1. The strbuf1 array contains digit characters and a space if the array contains non-digit characters. Then, when executing sprintf(strbuf, "%ux%ux8", xres, yres); more than 16 bytes will be written to strbuf. It is suggested to increase the size of the strbuf array to 24. Found by Linux Verification Center (linuxtesting.org) with SVACE. • https://git.kernel.org/stable/c/433c84c8495008922534c5cafdae6ff970fb3241 https://git.kernel.org/stable/c/57c4f4db0a194416da237fd09dad9527e00cb587 https://git.kernel.org/stable/c/252f147b1826cbb30ae0304cf86b66d3bb12b743 https://git.kernel.org/stable/c/41cf6f26abe4f491b694c54bd1aa2530369b7510 https://git.kernel.org/stable/c/889304120ecb2ca30674d89cd4ef15990b6a571c https://git.kernel.org/stable/c/688872c4ea4a528cd6a057d545c83506b533ee1f https://git.kernel.org/stable/c/11c0d49093b82f6c547fd419c41a982d26bdf5ef https://git.kernel.org/stable/c/9cf14f5a2746c19455ce9cb44341b5527 •

CVSS: -EPSS: 0%CPEs: 9EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: ceph: remove the incorrect Fw reference check when dirtying pages When doing the direct-io reads it will also try to mark pages dirty, but for the read path it won't hold the Fw caps and there is case will it get the Fw reference. • https://git.kernel.org/stable/c/5dda377cf0a6bd43f64a3c1efb670d7c668e7b29 https://git.kernel.org/stable/c/c26c5ec832dd9e9dcd0a0a892a485c99889b68f0 https://git.kernel.org/stable/c/126b567a2ef65fc38a71d832bf1216c56816f231 https://git.kernel.org/stable/c/f55e003d261baa7c57d51ae5c8ec1f5c26a35c89 https://git.kernel.org/stable/c/f863bfd0a2c6c99011c62ea71ac04f8e78707da9 https://git.kernel.org/stable/c/ea98284fc4fb05f276737d2043b02b62be5a8dfb https://git.kernel.org/stable/c/11ab19d48ab877430eed0c7d83810970bbcbc4f6 https://git.kernel.org/stable/c/9d4f619153bab7fa59736462967821d65 •

CVSS: -EPSS: 0%CPEs: 2EXPL: 0

In the Linux kernel, the following vulnerability has been resolved: cpufreq: loongson3: Use raw_smp_processor_id() in do_service_request() Use raw_smp_processor_id() instead of plain smp_processor_id() in do_service_request(), otherwise we may get some errors with the driver enabled: BUG: using smp_processor_id() in preemptible [00000000] code: (udev-worker)/208 caller is loongson3_cpufreq_probe+0x5c/0x250 [loongson3_cpufreq] • https://git.kernel.org/stable/c/2f78e4a6d2702ac03c2bf2ed3a0e344e1fa9f967 https://git.kernel.org/stable/c/2b7ec33e534f7a10033a5cf07794acf48b182bbe •