ptp: reject frequency adjustments that overflow scaled_ppm_to_ppb()
Subsystems (4)
v3 cover ptp: reject frequency adjustments that overflow scaled_ppm_to_ppb()
ptp_clock_adjtime() validates an ADJ_FREQUENCY request by converting tx->freq to ppb and comparing it against ops->max_adj. On 64-bit systems that conversion can overflow s64 and wrap the result back into range, so a crafted tx->freq bypasses the check and reaches ->adjfine() unclamped.
No real user space asks for such a frequency, so this is hardening rather than a fix anyone is waiting on, and it is targeted at net-next with no Fixes tag per Jakub's feedback on v2.
Patch 1 rejects the overflow in ptp_clock_adjtime().
Patch 2 adds a regression test that crafts struct timex.freq directly (testptp's int-ppb path cannot express the value) and confirms it is rejected with -ERANGE.
Changes in v3:
- retarget at net-next and drop the Fixes tag (Jakub Kicinski)
- patch 1: unchanged
- patch 2:
- cast the test value to the type of tx.freq rather than guarding on __SIZEOF_LONG__, which skipped the assignment on x32 and other y2038 configurations and failed the test there (Simon Horman)
- add the built binary to .gitignore
Changes in v2:
- patch 1: added Reviewed-by from Vadim Fedorenko.
- patch 2 (all from Simon Horman's review):
- cast fd to unsigned before the shift in FD_TO_CLOCKID (UBSan)
- avoid a -Woverflow warning on 32-bit
- save and restore the clock frequency
- skip instead of fail on -EBUSY (free-running clock)
Link to v1:
https://lore.kernel.org/netdev/[email protected]/
Link to v2:
https://lore.kernel.org/netdev/[email protected]/
Deep Shah (2):
ptp: reject frequency adjustments that overflow scaled_ppm_to_ppb()
selftests: ptp: add a regression test for the frequency adjustment
overflow
drivers/ptp/ptp_clock.c | 14 ++- tools/testing/selftests/ptp/.gitignore | 1 + tools/testing/selftests/ptp/Makefile | 2 +- .../testing/selftests/ptp/ptp_freq_overflow.c | 101 ++++++++++++++++++ 4 files changed, 116 insertions(+), 2 deletions(-) create mode 100644 tools/testing/selftests/ptp/ptp_freq_overflow.c
base-commit: 69963a0678a347d57c4ac8b16939dba216eb95ce
Signature · 1 line
2.43.0
PATCH v3 1/2 ptp: reject frequency adjustments that overflow scaled_ppm_to_ppb()
ptp_clock_adjtime() validates an ADJ_FREQUENCY request by converting the requested scaled ppm to ppb and comparing it against ops->max_adj:
long ppb = scaled_ppm_to_ppb(tx->freq); if (ppb > ops->max_adj || ppb < -ops->max_adj) return -ERANGE;
scaled_ppm_to_ppb() computes (1 + ppm) * 125 >> 13 in s64. For a sufficiently large tx->freq the multiplication overflows s64 and wraps, so the resulting ppb can fall back within [-max_adj, max_adj] and pass the check. The unclamped tx->freq is then handed to ->adjfine(), where drivers scale it again (e.g. scaled_ppm * 762939453125 in ptp_idt82p33) and program a bogus frequency word.
For example tx->freq = 147573952589676412 makes (1 + ppm) * 125 equal 2^64 + 9, which wraps to ppb == 0 and is accepted.
The caller already has write access to the PHC, so this hardens the max_adj sanity check rather than crossing a privilege boundary, and well-behaved user space (e.g. ptp4l) never requests such values. It is a follow-up to commit 475b92f93216 ("ptp: improve max_adj check against unreasonable values"), which handled the analogous s32 narrowing but not this multiplication overflow.
Detect the overflow with check_*_overflow() and reject the request in ptp_clock_adjtime() instead of acting on the wrapped value.
--- drivers/ptp/ptp_clock.c | 14 +++++++++++++- 1 file changed, 13 insertions(+), 1 deletion(-)
drivers/ptp/ptp_clock.c +13 -1
@@ -9,6 +9,7 @@#include <linux/init.h> #include <linux/kernel.h> #include <linux/module.h> +#include <linux/overflow.h> #include <linux/posix-clock.h> #include <linux/pps_kernel.h> #include <linux/property.h>
@@ -159,7 +160,18 @@ static int ptp_clock_adjtime(struct posix_clock *pc, struct __kernel_timex *tx) delta =ktime_to_ns (kt); err = ops->adjtime (ops, delta); }else if (tx->modes &ADJ_FREQUENCY ) { -long ppb =scaled_ppm_to_ppb (tx->freq); +long ppb; +s64 tmp; + +/* +* scaled_ppm_to_ppb() multiplies (1 + freq) by 125 in s64; +* reject a ->freq large enough to overflow that, which would +* otherwise wrap the result back into the max_adj range. +*/ +if (check_add_overflow ((s64 )tx->freq, (s64 )1 , &tmp) || +check_mul_overflow (tmp, (s64 )125 , &tmp)) +return -ERANGE ; + ppb =scaled_ppm_to_ppb (tx->freq);if (ppb > ops->max_adj || ppb < -ops->max_adj)return -ERANGE ; err = ops->adjfine (ops, tx->freq);
Signature · 1 line
2.43.0
Quoted 24 lines · Deep Shah
ptp_clock_adjtime()validates anADJ_FREQUENCYrequest by converting the requested scaled ppm to ppb and comparing it againstops->max_adj:long ppb = scaled_ppm_to_ppb(tx->freq); if (ppb > ops->max_adj || ppb < -ops->max_adj) return -ERANGE;
scaled_ppm_to_ppb()computes (1 + ppm) * 125 >> 13 in s64. For a sufficiently largetx->freqthe multiplication overflows s64 and wraps, so the resulting ppb can fall back within [-max_adj,max_adj] and pass the check. The unclampedtx->freqis then handed to ->adjfine(), where drivers scale it again (e.g.scaled_ppm* 762939453125 inptp_idt82p33) and program a bogus frequency word.For example
tx->freq= 147573952589676412 makes (1 + ppm) * 125 equal 2^64 + 9, which wraps to ppb == 0 and is accepted.The caller already has write access to the PHC, so this hardens the
max_adjsanity check rather than crossing a privilege boundary, and well-behaved user space (e.g. ptp4l) never requests such values. It is a follow-up to commit475b92f93216("ptp: improvemax_adjcheck against unreasonable values"), which handled the analogous s32 narrowing but not this multiplication overflow.
Quoted 5 lines
Detect the overflow with check_*_overflow() and reject the request in
ptp_clock_adjtime()instead of acting on the wrapped value.Signed-off-by Deep Shah <[email protected]>Reviewed-by Vadim Fedorenko <[email protected]>
PATCH v3 2/2 selftests: ptp: add a regression test for the frequency adjustment overflow
In reply to Deep Shahtestptp's -f option stores the requested adjustment as an int ppb and converts it to scaled ppm, so it cannot express the 64-bit scaled-ppm values needed to overflow scaled_ppm_to_ppb() and bypass the max_adj check enforced by ptp_clock_adjtime().
Add a small test that crafts struct timex.freq directly and verifies that an overflowing frequency adjustment is rejected with -ERANGE. The test skips when no frequency-adjustable PTP device is available.
--- tools/testing/selftests/ptp/.gitignore | 1 + tools/testing/selftests/ptp/Makefile | 2 +- .../testing/selftests/ptp/ptp_freq_overflow.c | 101 ++++++++++++++++++ 3 files changed, 103 insertions(+), 1 deletion(-) create mode 100644 tools/testing/selftests/ptp/ptp_freq_overflow.c
tools/testing/selftests/ptp/.gitignore +1 -0
@@ -1,2 +1,3 @@ # SPDX-License-Identifier: GPL-2.0-only testptp +ptp_freq_overflow
tools/testing/selftests/ptp/Makefile +1 -1
@@ -1,6 +1,6 @@ # SPDX-License-Identifier: GPL-2.0 CFLAGS += $(KHDR_INCLUDES) -TEST_GEN_PROGS := testptp +TEST_GEN_PROGS := testptp ptp_freq_overflow LDLIBS += -lrt TEST_PROGS = phc.sh
tools/testing/selftests/ptp/ptp_freq_overflow.c new file +101 -0
101 lines not on this page · raw message
Signature · 1 line
2.43.0
Re: [PATCH net-next v3 2/2] selftests: ptp: add a regression test for the frequency adjustment overflow
Quoted 10 lines · Deep Shah
testptp's -f option stores the requested adjustment as an int ppb and converts it to scaled ppm, so it cannot express the 64-bit scaled-ppm values needed to overflow
scaled_ppm_to_ppb()and bypass themax_adjcheck enforced byptp_clock_adjtime().Add a small test that crafts struct timex.freq directly and verifies that an overflowing frequency adjustment is rejected with
-ERANGE. The test skips when no frequency-adjustable PTP device is available.Signed-off-by Deep Shah <[email protected]>
Jakub Kicinski
maintainerQuoted 5 lines · On Sat, 1 Aug 2026 22:29:21 +0000 Deep Shah wrote:
- patch 2:
- cast the test value to the type of tx.freq rather than guarding on__SIZEOF_LONG__, which skipped the assignment on x32 and other y2038 configurations and failed the test there (Simon Horman)
- add the built binary to .gitignore
the test doesn't seem worth carrying in the tree TBH
If we really want this sort of unit test we should probably integrate it with more with the net side (the PTP target doesn't get run by netdev CI) and automatically create a netdevsim device which has a SW PTP etc. Again, not sure it's worth for a trival overflow test tho.
This series was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>:
Hello:
This series was applied to netdev/net-next.git (main) by Jakub Kicinski <[email protected]>:
Quoted 10 lines · On Sat, 1 Aug 2026 22:29:21 +0000 you wrote:
ptp_clock_adjtime()validates anADJ_FREQUENCYrequest by convertingtx->freqto ppb and comparing it againstops->max_adj. On 64-bit systems that conversion can overflow s64 and wrap the result back into range, so a craftedtx->freqbypasses the check and reaches ->adjfine() unclamped.No real user space asks for such a frequency, so this is hardening rather than a fix anyone is waiting on, and it is targeted at net-next with no Fixes tag per Jakub's feedback on v2.
[...]
Here is the summary with links:
- [net-next,v3,1/2] ptp: reject frequency adjustments that overflow scaled_ppm_to_ppb()
https://git.kernel.org/netdev/net-next/c/504ef04e8674
- [net-next,v3,2/2] selftests: ptp: add a regression test for the frequency adjustment overflow (no matching commit)
You are awesome, thank you!
Signature · 2 lines
Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html