Divya Chellam 4cf505e5e5 krb5: fix CVE-2025-24528
In MIT krb5 release 1.7 and later with incremental propagation
enabled, an authenticated attacker can cause kadmind to write beyond
the end of the mapped region for the iprop log file, likely causing a
process crash.

78ceba024b

Reference:
https://security-tracker.debian.org/tracker/CVE-2025-24528

Upstream-patch:
78ceba024b

Signed-off-by: Divya Chellam <divya.chellam@windriver.com>
Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
2025-09-26 13:17:09 +02:00
..
2023-12-13 13:35:51 -05:00
2024-10-13 11:19:52 -04:00
2025-09-18 11:49:40 +02:00

meta-oe
=======

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git
branch: kirkstone 

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit
e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed
packages to fullfit this might have different names on different host distributions
e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu
sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe][kirkstone]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][kirkstone][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded
to share your patches, this is preferred for patch sets consisting of more than one patch.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well,
'git fetch <remote>' works the same on all of them. We recommend GitHub because it is free, easy
to use, has been proven to be reliable and has a really good web GUI.

Layer maintainer: Gyorgy Sarvari <skandigraun@gmail.com>
Layer maintainer emeritus: Armin Kuster <akuster808@gmail.com>