Project

General

Profile

Actions

Bug #3278

closed

Disconnected ESME socket leaves esme entry in smsc->esme_list

Added by keith almost 6 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
SMPP Interface
Target version:
-
Start date:
05/17/2018
Due date:
% Done:

100%

Resolution:
Spec Reference:

Description

esme_link_read_cb() dead socket check in src/libmsc/smpp_smsc.c calls smpp_esme_put() but this does not result in removal of the esme from smsc->esme_list if there is more than one user.

This leads to the wqueue filling up, but because the socket is already gone it is never emptied leading to error messages such as: DLGLOBAL <001e> write_queue.c:112 wqueue(0x7f8bc392f6e0) is full. Rejecting msgb

This is static analysis, this same bug probably exists in legacy code in osmo-msc libmsc/smpp_smsc.c


Related issues

Related to OsmoMSC - Bug #5565: SMPP ESME heap-use-after-freeResolvedlaforge05/16/2022

Actions
Actions #1

Updated by keith over 2 years ago

  • Assignee set to keith

TODO: Check Is this still happening in libmsc. Otherwise close.

Actions #2

Updated by laforge almost 2 years ago

  • Project changed from OsmoNITB to OsmoMSC
  • Category set to SMPP Interface
Actions #3

Updated by laforge almost 2 years ago

  • Related to Bug #5565: SMPP ESME heap-use-after-free added
Actions #4

Updated by laforge almost 2 years ago

  • Status changed from New to In Progress
  • Assignee changed from keith to laforge
  • % Done changed from 0 to 80
Actions #5

Updated by laforge almost 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 80 to 100
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)