-
Bug
-
Resolution: Done-Errata
-
Normal
-
rhel-8.10.z
-
glibc-2.28-251.el8_10.16
-
None
-
Low
-
4bbca1a44691a6e9adcee5c6798a707b626bc331
-
2
-
rhel-pt-c-libs
-
ssg_platform_tools
-
1
-
False
-
False
-
-
No
-
Red Hat Enterprise Linux
-
PT Libraries 2025 S04, PT Libraries 2025 S05
-
Unspecified Release Note Type - Unknown
-
-
All
-
None
We should apply a cosmetic fix to the nscd code, correcting an oversight in timeout handling introduced by the fix for RHEL-34271:
diff --git a/nscd/netgroupcache.c b/nscd/netgroupcache.c index 4b35498e3f..5fdcf4204e 100644 --- a/nscd/netgroupcache.c +++ b/nscd/netgroupcache.c @@ -680,8 +680,8 @@ readdinnetgr (struct database_dyn *db, struct hashentry *he, .key_len = he->len }; - int timeout = addinnetgrX (db, -1, &req, db->data + he->key, he->owner, - he, dh); + time_t timeout = addinnetgrX (db, -1, &req, db->data + he->key, he->owner, + he, dh); if (timeout < 0) timeout = 0; return timeout;
Using int here should be harmless because the NSS service module does not control the timeout, and MAX_TIMEOUT_VALUE is not used. Valid timeout values are current time (in seconds since epoch) plus a few days at most (the default positive TTL is less than a day). This means that truncation does not happen during the supported time period of Red Hat Enterprise Linux 8, and the issue is cosmetic.
Upstream submission:
- links to
-
RHBA-2025:148073 updated rhel8/grafana container image
-
RHBA-2025:148075 updated rhel8/cups container image
-
RHBA-2025:148076 updated Red Hat Enterprise Linux 8 container images
-
RHBA-2025:148077 updated Red Hat Enterprise Linux 8 container images
-
RHBA-2025:148078 updated rhel8/gcc-toolset-13-toolchain container image
-
RHBA-2025:148079 updated rhel8/gcc-toolset-14-toolchain container image
-
RHBA-2025:148080 updated rhel8/go-toolset container image
-
RHBA-2025:148081 updated rhel8/memcached container image
-
RHBA-2025:148084 updated rhel8/pcp container image
-
RHBA-2025:148089 updated rhel8/tang container image
-
RHSA-2025:147940 glibc update